UltraVNC 1.0.1 Challenge Response Mechanism missing encryption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in UltraVNC 1.0.1. It has been rated as critical. This affects an unknown part of the component Challenge Response Mechanism. The manipulation leads to missing encryption. This vulnerability is referenced as CVE-2006-2206. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is advised.
Details
A vulnerability was found in UltraVNC 1.0.1 (Connectivity Software) and classified as critical. This issue affects an unknown function of the component Challenge Response Mechanism. The manipulation with an unknown input leads to a missing encryption vulnerability. Using CWE to declare the problem leads to CWE-311. The product does not encrypt sensitive or critical information before storage or transmission. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
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.
The weakness was published 05/05/2006 as confirmed posting (Bugtraq). The advisory is shared at archives.neohapsis.com. The identification of this vulnerability is CVE-2006-2206 since 05/04/2006. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1600 for this issue.
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (26283) and SecurityFocus (BID 17824†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Missing encryptionCWE: CWE-311 / CWE-310
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
05/03/2006 🔍05/04/2006 🔍
05/05/2006 🔍
05/05/2006 🔍
03/12/2015 🔍
02/24/2017 🔍
Sources
Advisory: archives.neohapsis.comStatus: Confirmed
CVE: CVE-2006-2206 (🔍)
GCVE (CVE): GCVE-0-2006-2206
GCVE (VulDB): GCVE-100-30065
X-Force: 26283 - Ultr@VNC MS-Logon weak encryption
SecurityFocus: 17824 - UltraVNC Weak Challenge-Response Authentication Vulnerability
Entry
Created: 03/12/2015 12:19Updated: 02/24/2017 13:11
Changes: 03/12/2015 12:19 (50), 02/24/2017 13:11 (5)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.