| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.9 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in SSH up to 1.2.31. Impacted is an unknown function of the component RC4 Encryption. This manipulation causes missing encryption. This vulnerability is handled as CVE-2001-1469. Additionally, an exploit exists. Due to its background and reception, this vulnerability has an historic impact. It is recommended to upgrade the affected component.
Details
A vulnerability was found in SSH up to 1.2.31 (SSH Server Software). It has been declared as critical. Affected by this vulnerability is some unknown processing of the component RC4 Encryption. The manipulation with an unknown input leads to a missing encryption vulnerability. The CWE definition for the vulnerability is CWE-311. The product does not encrypt sensitive or critical information before storage or transmission. As an impact it is known to affect confidentiality, and integrity. The summary by CVE is:
The RC4 stream cipher as used by SSH1 allows remote attackers to modify messages without detection by XORing the original message s cyclic redundancy check (CRC) with the CRC of a mask consisting of all the bits of the original message that were modified.
The weakness was released 01/18/2001 as confirmed advisory (CERT.org). It is possible to read the advisory at kb.cert.org. This vulnerability is known as CVE-2001-1469 since 04/21/2005. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are unknown but an exploit is available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 11/17/2024). The attack technique deployed by this issue is T1600 according to MITRE ATT&CK. Due to its background and reception, this vulnerability has a historic impact.
It is declared as proof-of-concept.
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at X-Force (6449). Entries connected to this vulnerability are available at VDB-16355, VDB-16354, VDB-16353 and VDB-16352. Be aware that VulDB is the high quality source for vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 5.9
VulDB Base Score: 6.5
VulDB Temp Score: 5.9
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: Proof-of-Concept
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
01/18/2001 🔍01/18/2001 🔍
04/21/2005 🔍
07/02/2014 🔍
11/17/2024 🔍
Sources
Advisory: kb.cert.orgStatus: Confirmed
CVE: CVE-2001-1469 (🔍)
GCVE (CVE): GCVE-0-2001-1469
GCVE (VulDB): GCVE-100-16351
CERT: 🔍
X-Force: 6449 - SSH1 with RC4 cipher could allow modification of packets
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 07/03/2014 00:56Updated: 11/17/2024 05:59
Changes: 07/03/2014 00:56 (48), 05/29/2018 09:18 (6), 11/17/2024 05:59 (17)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.