CVE-2005-2946
published 2005-09-16CVE-2005-2946: The default configuration on OpenSSL before 0.9.8 uses MD5 for creating message digests instead of a more cryptographically strong algorithm, which makes it…
PriorityP419high7.5CVSS 3.1
AVNACLPRNUINSUCNIHAN
EPSS
0.84%
53.8th percentile
The default configuration on OpenSSL before 0.9.8 uses MD5 for creating message digests instead of a more cryptographically strong algorithm, which makes it easier for remote attackers to forge certificates with a valid certificate authority signature.
Affected
8 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| canonical | ubuntu_linux | — | — |
| canonical | ubuntu_linux | — | — |
| debian | openssl | < openssl 0.9.8-1 (bookworm) | openssl 0.9.8-1 (bookworm) |
| openssl | openssl | < 0.9.8 | 0.9.8 |
| openssl | openssl | >= 0 < 0.9.8-1 | 0.9.8-1 |
| openssl | openssl | >= 0 < 0.9.8-1 | 0.9.8-1 |
| openssl | openssl | >= 0 < 0.9.8-1 | 0.9.8-1 |
| openssl | openssl | >= 0 < 0.9.8-1 | 0.9.8-1 |
CVSS provenance
nvdv3.17.5HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:N/I:P/A:N
osv7.5HIGH
vendor_cisco7.5HIGH
vendor_debian7.5LOW
vendor_redhat7.5HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Cisco
OpenSSL Version Rollback and Weak Cryptographic Algorithm Vulnerabilities
vendor_cisco·2005-10-12·CVSS 7.5
CVE-2005-2969 [HIGH] OpenSSL Version Rollback and Weak Cryptographic Algorithm Vulnerabilities
OpenSSL Version Rollback and Weak Cryptographic Algorithm Vulnerabilities
OpenSSL contains vulnerabilities that could allow an unauthenticated, remote attacker to bypass security restrictions.
The first vulnerability (CVE-2005-2969) affects any application using a SL/TLS server implementation provided by OpenSSL versions 0.9.7g and prior. If these implementations have options designed to mitigate third party bugs enabled, a remote attacker conducting a man-in-the-middle attack could force connections between the hosts to use the 2.0 version of the SSL protocol. A known cryptographic weaknesses exists in the SSL 2.0 protocol.
The second vulnerability (CVE-2005-2946) exists in the default configuration of OpenSSL versions prior to 0.9.8a. This configuration creates message digests using MD5
Debian
CVE-2005-2946: openssl - The default configuration on OpenSSL before 0.9.8 uses MD5 for creating message ...
vendor_debian·2005·CVSS 7.5
CVE-2005-2946 [HIGH] CVE-2005-2946: openssl - The default configuration on OpenSSL before 0.9.8 uses MD5 for creating message ...
The default configuration on OpenSSL before 0.9.8 uses MD5 for creating message digests instead of a more cryptographically strong algorithm, which makes it easier for remote attackers to forge certificates with a valid certificate authority signature.
Scope: local
bookworm: resolved (fixed in 0.9.8-1)
bullseye: resolved (fixed in 0.9.8-1)
forky: resolved (fixed in 0.9.8-1)
sid: resolved (fixed in 0.9.8-1)
trixie: resolved (fixed in 0.9.8-1)
Red Hat
CVE-2005-2946: The default configuration on OpenSSL before 0
vendor_redhat·CVSS 7.5
CVE-2005-2946 [HIGH] CVE-2005-2946: The default configuration on OpenSSL before 0
The default configuration on OpenSSL before 0.9.8 uses MD5 for creating message digests instead of a more cryptographically strong algorithm, which makes it easier for remote attackers to forge certificates with a valid certificate authority signature.
Statement: Red Hat is aware of this issue and is tracking it via the following bug:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169803
The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw. More information regarding issue severity can be found here:
http://www.redhat.com/security/updates/classification/
GHSA
GHSA-frvr-h7xx-w54m: The default configuration on OpenSSL before 0
ghsa_unreviewed·2022-05-01
CVE-2005-2946 [MEDIUM] CWE-327 GHSA-frvr-h7xx-w54m: The default configuration on OpenSSL before 0
The default configuration on OpenSSL before 0.9.8 uses MD5 for creating message digests instead of a more cryptographically strong algorithm, which makes it easier for remote attackers to forge certificates with a valid certificate authority signature.
OSV
CVE-2005-2946: The default configuration on OpenSSL before 0
osv·2005-09-16·CVSS 7.5
CVE-2005-2946 [HIGH] CVE-2005-2946: The default configuration on OpenSSL before 0
The default configuration on OpenSSL before 0.9.8 uses MD5 for creating message digests instead of a more cryptographically strong algorithm, which makes it easier for remote attackers to forge certificates with a valid certificate authority signature.
No detection rules found.
No public exploits indexed.
CWE
Use of a Cryptographic Primitive with a Risky Implementation
mitre_cwe
CWE-1240 Use of a Cryptographic Primitive with a Risky Implementation
CWE-1240: Use of a Cryptographic Primitive with a Risky Implementation
To fulfill the need for a cryptographic primitive, the product implements a cryptographic algorithm using a non-standard, unproven, or disallowed/non-compliant cryptographic implementation.
Cryptographic protocols and systems depend on cryptographic primitives (and associated algorithms) as their basic building blocks. Some common examples of primitives are digital signatures, one-way hash functions, ciphers, and public key cryptography; however, the notion of "primitive" can vary depending on point of view. See "Terminology Notes" for further explanation of some concepts. Cryptographic primitives are defined to accomplish one very specific task in a precisely defined and mathematically reliable fashion. For example,
CWE
Use of a Broken or Risky Cryptographic Algorithm
mitre_cwe
CWE-327 Use of a Broken or Risky Cryptographic Algorithm
CWE-327: Use of a Broken or Risky Cryptographic Algorithm
The product uses a broken or risky cryptographic algorithm or protocol.
Cryptographic algorithms are the methods by which data is scrambled to prevent observation or influence by unauthorized actors. Insecure cryptography can be exploited to expose sensitive information, modify data in unexpected ways, spoof identities of other users or devices, or other impacts. It is very difficult to produce a secure algorithm, and even high-profile algorithms by accomplished cryptographic experts have been broken. Well-known techniques exist to break or weaken various kinds of cryptography. Accordingly, there are a small number of well-understood and heavily studied algorithms that should be used by most products. Using a non-standard or known
2005-09-16
Published