blob: eb132e99ada69a4a0d7a6b3b0ea6d5b3eb25f0e0 [file] [log] [blame]
<?xml version="1.0" encoding="utf-8"?>
<glsa id="200807-07">
<title>NX: User-assisted execution of arbitrary code</title>
NX uses code from the X11 server which is prone to multiple
<product type="ebuild">nx, nxnode</product>
<announced>July 09, 2008</announced>
<revised>July 09, 2008: 01</revised>
<package name="net-misc/nxnode" auto="yes" arch="*">
<unaffected range="ge">3.2.0-r3</unaffected>
<vulnerable range="lt">3.2.0-r3</vulnerable>
<package name="net-misc/nx" auto="yes" arch="*">
<unaffected range="ge">3.2.0-r2</unaffected>
<vulnerable range="lt">3.2.0-r2</vulnerable>
NoMachine's NX establishes remote connections to X11 desktops over
small bandwidth links. NX and NX Node are the compression core
libraries, whereas NX is used by FreeNX and NX Node by the binary-only
NX servers.
Multiple integer overflow and buffer overflow vulnerabilities have been
discovered in the X.Org X server as shipped by NX and NX Node (GLSA
<impact type="normal">
A remote attacker could exploit these vulnerabilities via unspecified
vectors, leading to the execution of arbitrary code with the privileges
of the user on the machine running the NX server.
There is no known workaround at this time.
All NX Node users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose &quot;&gt;=net-misc/nxnode-3.2.0-r3&quot;</code>
All NX users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose &quot;&gt;=net-misc/nx-3.2.0-r2&quot;</code>
<uri link="/security/en/glsa/glsa-200806-07.xml">GLSA 200806-07</uri>
<metadata tag="submitter" timestamp="Mon, 07 Jul 2008 00:06:37 +0000">
<metadata tag="bugReady" timestamp="Mon, 07 Jul 2008 00:06:48 +0000">