From owner-freebsd-security@freebsd.org  Wed Jul  3 01:55:34 2019
Return-Path: <owner-freebsd-security@freebsd.org>
Delivered-To: freebsd-security@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3FA6815E6F27
 for <freebsd-security@mailman.ysv.freebsd.org>;
 Wed,  3 Jul 2019 01:55:34 +0000 (UTC)
 (envelope-from rfg@tristatelogic.com)
Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com
 [69.62.255.118])
 by mx1.freebsd.org (Postfix) with ESMTP id DE43084B0F
 for <freebsd-security@freebsd.org>; Wed,  3 Jul 2019 01:55:32 +0000 (UTC)
 (envelope-from rfg@tristatelogic.com)
Received: by segfault.tristatelogic.com (Postfix, from userid 1237)
 id 5F4FD4E70C; Tue,  2 Jul 2019 18:55:26 -0700 (PDT)
From: "Ronald F. Guilmette" <rfg@tristatelogic.com>
To: freebsd-security@freebsd.org
Subject: Re: FreeBSD Security Advisory FreeBSD-SA-19:11.cd_ioctl
In-Reply-To: <20190703004928.576CA1A7DE@freefall.freebsd.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <12531.1562118926.1@segfault.tristatelogic.com>
Date: Tue, 02 Jul 2019 18:55:26 -0700
Message-ID: <12532.1562118926@segfault.tristatelogic.com>
X-Rspamd-Queue-Id: DE43084B0F
X-Spamd-Bar: ------
Authentication-Results: mx1.freebsd.org;
 spf=pass (mx1.freebsd.org: domain of rfg@tristatelogic.com designates
 69.62.255.118 as permitted sender) smtp.mailfrom=rfg@tristatelogic.com
X-Spamd-Result: default: False [-6.09 / 15.00]; ARC_NA(0.00)[];
 NEURAL_HAM_MEDIUM(-1.00)[-0.996,0]; FROM_HAS_DN(0.00)[];
 R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[];
 MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[];
 DMARC_NA(0.00)[tristatelogic.com]; RCPT_COUNT_ONE(0.00)[1];
 NEURAL_HAM_LONG(-1.00)[-1.000,0];
 IP_SCORE(-2.90)[ip: (-7.61), ipnet: 69.62.128.0/17(-3.81), asn: 14051(-3.02),
 country: US(-0.06)]; MX_GOOD(-0.01)[mx1.tristatelogic.com];
 NEURAL_HAM_SHORT(-0.98)[-0.982,0]; RCVD_NO_TLS_LAST(0.10)[];
 FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[];
 MIME_TRACE(0.00)[0:+];
 ASN(0.00)[asn:14051, ipnet:69.62.128.0/17, country:US];
 RCVD_COUNT_TWO(0.00)[2]
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Security issues \[members-only posting\]"
 <freebsd-security.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security/>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Jul 2019 01:55:34 -0000

In message <20190703004928.576CA1A7DE@freefall.freebsd.org>, 
freebsd-security@freebsd.org wrote:

>Topic:          Privilege escalation in cd(4) driver
>...
>devfs.conf(5) and devfs.rules(5) can be used to remove read permissions from
>cd(4) devices.

Would it be accurate to say that another possible workaround would be to
simply remove the optical drive from the system(s) entirely?

(I dunno about anybody else, but I personally don't even hardly use the
bloody things anymore anyway.)