| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.8 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in TightVNC 1.2/1.2.1/1.2.2/1.2.3 on Windows and classified as problematic. Affected is an unknown function. Performing a manipulation results in missing encryption. This vulnerability is identified as CVE-2002-1848. There is not any exploit available. The affected component should be upgraded.
Details
A vulnerability was found in TightVNC 1.2/1.2.1/1.2.2/1.2.3 on Windows. It has been classified as problematic. This affects an unknown part. The manipulation with an unknown input leads to a missing encryption vulnerability. CWE is classifying the issue as CWE-311. The product does not encrypt sensitive or critical information before storage or transmission. This is going to have an impact on confidentiality. The summary by CVE is:
TightVNC before 1.2.4 running on Windows stores unencrypted passwords in the password text control of the WinVNC Properties dialog, which could allow local users to access passwords.
The weakness was released 12/31/2002 (Website). It is possible to read the advisory at tightvnc.com. This vulnerability is uniquely identified as CVE-2002-1848 since 06/29/2005. The exploitability is told to be easy. Attacking locally is a requirement. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1600 according to MITRE ATT&CK.
Upgrading to version 1.2.4 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 4835†). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.0VulDB Meta Temp Score: 3.8
VulDB Base Score: 4.0
VulDB Temp Score: 3.8
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: Partially
Local: Yes
Remote: No
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: 🔍
Upgrade: TightVNC 1.2.4
Timeline
05/25/2002 🔍12/31/2002 🔍
12/31/2002 🔍
06/29/2005 🔍
08/04/2014 🔍
06/10/2018 🔍
Sources
Advisory: tightvnc.comStatus: Not defined
Confirmation: 🔍
CVE: CVE-2002-1848 (🔍)
GCVE (CVE): GCVE-0-2002-1848
GCVE (VulDB): GCVE-100-19491
SecurityFocus: 4835 - TightVNC Plain Text Password Storage Vulnerability
Entry
Created: 08/04/2014 17:15Updated: 06/10/2018 08:55
Changes: 08/04/2014 17:15 (46), 06/10/2018 08:55 (6)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.