From: "Sergey Popov (pinkbyte)" <pinkbyte@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo commit in xml/htdocs/security/en/glsa: glsa-201402-02.xml
Date: Sun, 2 Feb 2014 17:55:26 +0000 (UTC) [thread overview]
Message-ID: <20140202175526.C58442004C@flycatcher.gentoo.org> (raw)
pinkbyte 14/02/02 17:55:26
Added: glsa-201402-02.xml
Log:
GLSA 201402-02
Revision Changes Path
1.1 xml/htdocs/security/en/glsa/glsa-201402-02.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/security/en/glsa/glsa-201402-02.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/security/en/glsa/glsa-201402-02.xml?rev=1.1&content-type=text/plain
Index: glsa-201402-02.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/xsl/glsa.xsl" type="text/xsl"?>
<?xml-stylesheet href="/xsl/guide.xsl" type="text/xsl"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="201402-02">
<title>NVIDIA Drivers: Privilege Escalation</title>
<synopsis>A NVIDIA drivers bug allows unprivileged user-mode software to
access the GPU inappropriately, allowing for privilege escalation.
</synopsis>
<product type="ebuild">nvidia-drivers</product>
<announced>February 02, 2014</announced>
<revised>February 02, 2014: 1</revised>
<bug>493448</bug>
<access>local</access>
<affected>
<package name="x11-drivers/nvidia-drivers" auto="yes" arch="*">
<unaffected range="ge">331.20</unaffected>
<unaffected range="rge">319.76</unaffected>
<unaffected range="rge">304.116</unaffected>
<vulnerable range="lt">331.20</vulnerable>
</package>
</affected>
<background>
<p>The NVIDIA drivers provide X11 and GLX support for NVIDIA graphic
boards.
</p>
</background>
<description>
<p>The vulnerability is caused due to the driver allowing unprivileged
user-mode software to access the GPU.
</p>
</description>
<impact type="high">
<p>A local attacker could gain escalated privileges.</p>
</impact>
<workaround>
<p>There is no known workaround at this time.</p>
</workaround>
<resolution>
<p>All NVIDIA Drivers users using the 331 branch should upgrade to the
latest version:
</p>
<code>
# emerge --sync
# emerge --ask --oneshot --verbose
">=x11-drivers/nvidia-drivers-331.20"
</code>
<p>All NVIDIA Drivers users using the 319 branch should upgrade to the
latest version:
</p>
<code>
# emerge --sync
# emerge --ask --oneshot --verbose
">=x11-drivers/nvidia-drivers-319.76"
</code>
<p>All NVIDIA Drivers users using the 304 branch should upgrade to the
latest version:
</p>
<code>
# emerge --sync
# emerge --ask --oneshot --verbose
">=x11-drivers/nvidia-drivers-304.116"
</code>
</resolution>
<references>
<uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-5987">CVE-2013-5987</uri>
</references>
<metadata tag="requester" timestamp="Sat, 14 Dec 2013 04:12:07 +0000">
BlueKnight
</metadata>
<metadata tag="submitter" timestamp="Sun, 02 Feb 2014 17:54:59 +0000">
BlueKnight
</metadata>
</glsa>
next reply other threads:[~2014-02-02 17:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-02 17:55 Sergey Popov (pinkbyte) [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-02-02 18:03 [gentoo-commits] gentoo commit in xml/htdocs/security/en/glsa: glsa-201402-02.xml Sergey Popov (pinkbyte)
2014-03-13 6:55 Sergey Popov (pinkbyte)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140202175526.C58442004C@flycatcher.gentoo.org \
--to=pinkbyte@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox