First published: Mon Mar 03 2003(Updated: )
The vncserver wrapper for vnc before 3.3.3r2-21 uses the rand() function instead of srand(), which causes vncserver to generate weak cookies.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
AT&T VNC | =3.3.3 | |
AT&T VNC | =3.3.3r2 | |
AT&T VNC | =3.3.4 | |
AT&T VNC | =3.3.5 | |
AT&T VNC | =3.3.6 | |
TightVNC | =1.2.0 | |
TightVNC | =1.2.1 | |
TightVNC | =1.2.2 | |
TightVNC | =1.2.3 | |
TightVNC | =1.2.4 | |
TightVNC | =1.2.5 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2002-1511 is classified as a moderate severity vulnerability due to the weak cookie generation that could lead to unauthorized access.
To fix CVE-2002-1511, upgrade to a version of VNC that is 3.3.3r2-21 or later, or use a patched version.
CVE-2002-1511 affects versions of AT&T VNC prior to 3.3.3r2-21 and certain versions of TightVNC.
Exploiting CVE-2002-1511 can allow an attacker to gain unauthorized access to a VNC session due to weak cookie security.
While CVE-2002-1511 primarily affects older VNC versions, any outdated systems running these versions are still at risk.