What is the severity of CVE-2002-1336?

CVE-2002-1336 is considered a high-severity vulnerability due to its potential for allowing unauthorized remote access.

How do I fix CVE-2002-1336?

To fix CVE-2002-1336, upgrade TightVNC to version 1.2.6 or later to ensure unique challenge strings for each connection.

Which versions of TightVNC are affected by CVE-2002-1336?

TightVNC versions 1.2.0 through 1.2.5 are affected by CVE-2002-1336.

Is it safe to use TightVNC versions prior to 1.2.6 due to CVE-2002-1336?

No, using TightVNC versions prior to 1.2.6 is not safe due to the vulnerability allowing potential unauthorized access.

Vulnerability/
CVE-2002-1336

high

7.5

CWE

NVD-CWE-Other

11/12/2002

1/9/2004

8/8/2024

CVE-2002-1336

First published: Wed Dec 11 2002(Updated: )

TightVNC before 1.2.6 generates the same challenge string for multiple connections, which allows remote attackers to bypass VNC authentication by sniffing the challenge and response of other users.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
TightVNC	=1.2.4
TightVNC	=1.2.0
TightVNC	=1.2.1
TightVNC	=1.2.3
TightVNC	=1.2.5

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2002-1336?
CVE-2002-1336 is considered a high-severity vulnerability due to its potential for allowing unauthorized remote access.
How do I fix CVE-2002-1336?
To fix CVE-2002-1336, upgrade TightVNC to version 1.2.6 or later to ensure unique challenge strings for each connection.
Which versions of TightVNC are affected by CVE-2002-1336?
TightVNC versions 1.2.0 through 1.2.5 are affected by CVE-2002-1336.
What type of attack does CVE-2002-1336 enable?
CVE-2002-1336 enables remote attackers to bypass VNC authentication by sniffing challenge and response data.
Is it safe to use TightVNC versions prior to 1.2.6 due to CVE-2002-1336?
No, using TightVNC versions prior to 1.2.6 is not safe due to the vulnerability allowing potential unauthorized access.

agent/type
agent/first-publish-date
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/references
agent/severity
agent/weakness
agent/last-modified-date
agent/author
agent/description
agent/event
agent/source
agent/tags
collector/nvd-historical
vendor/tightvnc
product/tightvnc
canonical/tightvnc tightvnc
agent/software-canonical-lookup-request
collector/nvd-index
canonical/tightvnc
version/tightvnc/1.2.4
version/tightvnc/1.2.0
version/tightvnc/1.2.1
version/tightvnc/1.2.3
version/tightvnc/1.2.5

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2002-1336?
CVE-2002-1336 is considered a high-severity vulnerability due to its potential for allowing unauthorized remote access.
How do I fix CVE-2002-1336?
To fix CVE-2002-1336, upgrade TightVNC to version 1.2.6 or later to ensure unique challenge strings for each connection.
Which versions of TightVNC are affected by CVE-2002-1336?
TightVNC versions 1.2.0 through 1.2.5 are affected by CVE-2002-1336.
What type of attack does CVE-2002-1336 enable?
CVE-2002-1336 enables remote attackers to bypass VNC authentication by sniffing challenge and response data.
Is it safe to use TightVNC versions prior to 1.2.6 due to CVE-2002-1336?
No, using TightVNC versions prior to 1.2.6 is not safe due to the vulnerability allowing potential unauthorized access.

CVE-2002-1336

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2002-1336?

How do I fix CVE-2002-1336?

Which versions of TightVNC are affected by CVE-2002-1336?

What type of attack does CVE-2002-1336 enable?

Is it safe to use TightVNC versions prior to 1.2.6 due to CVE-2002-1336?

Company

Resources

Contact

Frequently Asked Questions

What is the severity of CVE-2002-1336?

How do I fix CVE-2002-1336?

Which versions of TightVNC are affected by CVE-2002-1336?

What type of attack does CVE-2002-1336 enable?

Is it safe to use TightVNC versions prior to 1.2.6 due to CVE-2002-1336?