CVE-2004-2761
published 2009-01-05CVE-2004-2761: The MD5 Message-Digest Algorithm is not collision resistant, which makes it easier for context-dependent attackers to conduct spoofing attacks, as demonstrated…
PriorityP347critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
EXPLOIT
EPSS
9.85%
95.0th percentile
The MD5 Message-Digest Algorithm is not collision resistant, which makes it easier for context-dependent attackers to conduct spoofing attacks, as demonstrated by attacks on the use of MD5 in the signature algorithm of an X.509 certificate.
Affected
1 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| github.com | sylabs_sif_v2 | >= 0 < 2.8.1 | 2.8.1 |
CVSS provenance
nvdv3.19.8CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:N/I:P/A:N
ghsa5.0MEDIUM
osv5.0MEDIUM
vendor_redhat5.0MEDIUM
CVEs like this are exactly what “Exploited This Week” covers.
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.
Ubuntu
NSS vulnerability
vendor_ubuntu·2009-03-17
CVE-2004-2761 NSS vulnerability
Title: NSS vulnerability
Summary: NSS vulnerability
The MD5 algorithm is known not to be collision resistant. This update
blocklists the proof of concept rogue certificate authority as discussed
in http://www.win.tue.nl/hashclash/rogue-ca/.
Instructions: After a standard system upgrade you need to restart your session to
effect the necessary changes.
Red Hat
MD5: MD5 Message-Digest Algorithm is not collision resistant
vendor_redhat·2008-12-30·CVSS 5.0
CVE-2004-2761 [MEDIUM] MD5: MD5 Message-Digest Algorithm is not collision resistant
MD5: MD5 Message-Digest Algorithm is not collision resistant
The MD5 Message-Digest Algorithm is not collision resistant, which makes it easier for context-dependent attackers to conduct spoofing attacks, as demonstrated by attacks on the use of MD5 in the signature algorithm of an X.509 certificate.
Statement: Please see https://access.redhat.com/solutions/15378
GHSA
SIF's Digital Signature Hash Algorithms Not Validated
ghsa·2022-10-06·CVSS 5.0
CVE-2022-39237 [MEDIUM] CWE-327 SIF's Digital Signature Hash Algorithms Not Validated
SIF's Digital Signature Hash Algorithms Not Validated
### Impact
The `github.com/sylabs/sif/v2/pkg/integrity` package does not verify that the hash algorithm(s) used are cryptographically secure when verifying digital signatures.
### Patches
A patch is available in version >= v2.8.1 of the module. Users are encouraged to upgrade.
The patch is commit https://github.com/sylabs/sif/commit/07fb86029a12e3210f6131e065570124605daeaa
### Workarounds
Users may independently validate that the hash algorithm(s) used for metadata digest(s) and signature hash are cryptographically secure.
### References
* [CVE-2004-2761](https://nvd.nist.gov/vuln/detail/cve-2004-2761)
* [CVE-2005-4900](https://nvd.nist.gov/vuln/detail/cve-2005-4900)
### For more information
If you have any questions or comme
OSV
SIF's Digital Signature Hash Algorithms Not Validated
osv·2022-10-06·CVSS 5.0
CVE-2022-39237 [MEDIUM] SIF's Digital Signature Hash Algorithms Not Validated
SIF's Digital Signature Hash Algorithms Not Validated
### Impact
The `github.com/sylabs/sif/v2/pkg/integrity` package does not verify that the hash algorithm(s) used are cryptographically secure when verifying digital signatures.
### Patches
A patch is available in version >= v2.8.1 of the module. Users are encouraged to upgrade.
The patch is commit https://github.com/sylabs/sif/commit/07fb86029a12e3210f6131e065570124605daeaa
### Workarounds
Users may independently validate that the hash algorithm(s) used for metadata digest(s) and signature hash are cryptographically secure.
### References
* [CVE-2004-2761](https://nvd.nist.gov/vuln/detail/cve-2004-2761)
* [CVE-2005-4900](https://nvd.nist.gov/vuln/detail/cve-2005-4900)
### For more information
If you have any questions or comme
GHSA
GHSA-2q4p-93p8-q2j6: The MD5 Message-Digest Algorithm is not collision resistant, which makes it easier for context-dependent attackers to conduct spoofing attacks, as dem
ghsa_unreviewed·2022-04-29
CVE-2004-2761 [MEDIUM] GHSA-2q4p-93p8-q2j6: The MD5 Message-Digest Algorithm is not collision resistant, which makes it easier for context-dependent attackers to conduct spoofing attacks, as dem
The MD5 Message-Digest Algorithm is not collision resistant, which makes it easier for context-dependent attackers to conduct spoofing attacks, as demonstrated by attacks on the use of MD5 in the signature algorithm of an X.509 certificate.
No detection rules found.
arXiv
On managing vulnerabilities in AI/ML systems
arxiv_fulltext·2021-01-22
On managing vulnerabilities in AI/ML systems
On managing vulnerabilities in AI/ML systems
Jonathan M. Spring
jspring AT sei dot cmu dot edu
0000-0001-9356-219X
CERT Coordination Center\ Engineering Institute\ Mellon University
Pittsburgh
PA
15213
April Galyardt
Software Engineering Institute\ Mellon University
Pittsburgh
PA
15213
Allen D. Householder
0000-0001-8970-4108
CERT Coordination Center\ Engineering Institute\ Mellon University
Pittsburgh
PA
15213
Nathan VanHoudnos
Software Engineering Institute\ Mellon University
Pittsburgh
PA
15213
Spring, Galyardt, Householder, and VanHoudnos
## Abstract
This paper explores how the current paradigm of vulnerability management might adapt to include machine learning systems through a
thought experiment: what if flaws in *ML were assigned *CVE-ID?
We consider both *ML algorithms a
Bugzilla
CVE-2004-2761 MD5: MD5 Message-Digest Algorithm is not collision resistant
bugzilla·2010-11-02·CVSS 5.0
CVE-2004-2761 [MEDIUM] CVE-2004-2761 MD5: MD5 Message-Digest Algorithm is not collision resistant
CVE-2004-2761 MD5: MD5 Message-Digest Algorithm is not collision resistant
Common Vulnerabilities and Exposures assigned an identifier CVE-2004-2761 to the following vulnerability:
The MD5 Message-Digest Algorithm is not collision resistant, which makes it easier for context-dependent attackers to conduct spoofing attacks, as demonstrated by attacks on the use of MD5 in the signature algorithm of an X.509 certificate.
References:
http://www.kb.cert.org/vuls/id/836068
http://eprint.iacr.org/2004/199
http://eprint.iacr.org/2005/067
http://www.win.tue.nl/hashclash/rogue-ca/
http://www.phreedom.org/research/rogue-ca/
http://blog.mozilla.com/security/2008/12/30/md5-weaknesses-could-lead-to-certificate-forgery/
Discussion:
As noted in the Knowledgebase article, Red Hat Certificate System is
CAPEC
Creating a Rogue Certification Authority Certificate
mitre_capec
[CRITICAL] Creating a Rogue Certification Authority Certificate
CAPEC-459: Creating a Rogue Certification Authority Certificate
An adversary exploits a weakness resulting from using a hashing algorithm with weak collision resistance to generate certificate signing requests (CSR) that contain collision blocks in their "to be signed" parts. The adversary submits one CSR to be signed by a trusted certificate authority then uses the signed blob to make a second certificate appear signed by said certificate authority. Due to the hash collision, both certificates, though different, hash to the same value and so the signed blob works just as well in the second certificate. The net effect is that the adversary's second X.509 certificate, which the Certification Authority has never seen, is now signed and validated by that Certification Authority.
Execution F
http://blog.mozilla.com/security/2008/12/30/md5-weaknesses-could-lead-to-certificate-forgery/http://blogs.technet.com/swi/archive/2008/12/30/information-regarding-md5-collisions-problem.aspxhttp://secunia.com/advisories/33826http://secunia.com/advisories/34281http://secunia.com/advisories/42181http://securityreason.com/securityalert/4866http://securitytracker.com/id?1024697http://www.cisco.com/en/US/products/products_security_response09186a0080a5d24a.htmlhttp://www.doxpara.com/research/md5/md5_someday.pdfhttp://www.kb.cert.org/vuls/id/836068http://www.microsoft.com/technet/security/advisory/961509.mspxhttp://www.phreedom.org/research/rogue-ca/http://www.securityfocus.com/archive/1/499685/100/0/threadedhttp://www.securityfocus.com/bid/33065http://www.ubuntu.com/usn/usn-740-1http://www.win.tue.nl/hashclash/SoftIntCodeSign/http://www.win.tue.nl/hashclash/rogue-ca/https://blogs.verisign.com/ssl-blog/2008/12/on_md5_vulnerabilities_and_mit.phphttps://bugzilla.redhat.com/show_bug.cgi?id=648886https://h20566.www2.hpe.com/portal/site/hpsc/public/kb/docDisplay?docId=emr_na-c05289935https://h20566.www2.hpe.com/portal/site/hpsc/public/kb/docDisplay?docId=emr_na-c05336888https://ics-cert.us-cert.gov/advisories/ICSMA-18-058-02https://rhn.redhat.com/errata/RHSA-2010-0837.htmlhttps://rhn.redhat.com/errata/RHSA-2010-0838.htmlhttps://support.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-hpesbhf03814en_ushttps://www.redhat.com/archives/fedora-package-announce/2009-February/msg00096.htmlhttp://blog.mozilla.com/security/2008/12/30/md5-weaknesses-could-lead-to-certificate-forgery/http://blogs.technet.com/swi/archive/2008/12/30/information-regarding-md5-collisions-problem.aspxhttp://secunia.com/advisories/33826http://secunia.com/advisories/34281http://secunia.com/advisories/42181http://securityreason.com/securityalert/4866http://securitytracker.com/id?1024697http://www.cisco.com/en/US/products/products_security_response09186a0080a5d24a.htmlhttp://www.doxpara.com/research/md5/md5_someday.pdfhttp://www.kb.cert.org/vuls/id/836068http://www.microsoft.com/technet/security/advisory/961509.mspxhttp://www.phreedom.org/research/rogue-ca/http://www.securityfocus.com/archive/1/499685/100/0/threadedhttp://www.securityfocus.com/bid/33065http://www.ubuntu.com/usn/usn-740-1http://www.win.tue.nl/hashclash/SoftIntCodeSign/http://www.win.tue.nl/hashclash/rogue-ca/https://blogs.verisign.com/ssl-blog/2008/12/on_md5_vulnerabilities_and_mit.phphttps://bugzilla.redhat.com/show_bug.cgi?id=648886https://h20566.www2.hpe.com/portal/site/hpsc/public/kb/docDisplay?docId=emr_na-c05289935https://h20566.www2.hpe.com/portal/site/hpsc/public/kb/docDisplay?docId=emr_na-c05336888https://ics-cert.us-cert.gov/advisories/ICSMA-18-058-02https://rhn.redhat.com/errata/RHSA-2010-0837.htmlhttps://rhn.redhat.com/errata/RHSA-2010-0838.htmlhttps://support.hpe.com/hpsc/doc/public/display?docLocale=en_US&docId=emr_na-hpesbhf03814en_ushttps://www.redhat.com/archives/fedora-package-announce/2009-February/msg00096.html
2009-01-05
Published