CVE-2006-2206: Weak Encryption
First published: Fri May 05 2006(Updated: )
The MS-Logon authentication scheme in UltraVNC (aka Ultr@VNC) 1.0.1 uses weak encryption (XOR) for challenge/response, which allows remote attackers to gain privileges by sniffing and decrypting passwords.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| UltraVNC UltraVNC | =1.0.1 | |
| UltraVNC | =1.0.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2006-2206?
CVE-2006-2206 is considered to have a high severity due to the use of weak encryption in the MS-Logon authentication scheme.
How do I fix CVE-2006-2206?
To fix CVE-2006-2206, users should upgrade to a newer version of UltraVNC that does not utilize weak encryption.
What types of attacks can exploit CVE-2006-2206?
CVE-2006-2206 can be exploited by remote attackers who can sniff network traffic to decrypt user passwords.
What software is affected by CVE-2006-2206?
CVE-2006-2206 specifically affects UltraVNC version 1.0.1.
How does CVE-2006-2206 impact user security?
CVE-2006-2206 impacts user security by allowing unauthorized privilege escalation through compromised passwords.
- agent/type
- agent/first-publish-date
- agent/last-modified-date
- agent/weakness
- agent/references
- agent/author
- agent/description
- collector/nvd-historical
- agent/software-canonical-lookup-request
- agent/severity
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/event
- vendor/ultravnc
- canonical/ultravnc ultravnc
- version/ultravnc ultravnc/1.0.1
- canonical/ultravnc
- version/ultravnc/1.0.1