CVE-2009-2973 json
Google Chrome before 2.0.172.43 does not prevent SSL connections to a site with an X.509 certificate signed with the (1) MD2 or (2) MD4 alg…
published 17y ago modified 5mo ago also EUVD-2009-2958
- cvss
- 6.4
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 61%
- public exploits
- 0
- none known
Summary
Google Chrome before 2.0.172.43 does not prevent SSL connections to a site with an X.509 certificate signed with the (1) MD2 or (2) MD4 algorithm, which makes it easier for man-in-the-middle attackers to spoof arbitrary HTTPS servers via a crafted certificate, a related issue to CVE-2009-2409.
Patch / fix
- google chrome 2.0.172.43
Is CVE-2009-2973 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.93% chance of exploitation in the next 30 days, higher than 61% of all scored CVEs (FIRST EPSS, 2026-11-16).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.4 | AV:N/AC:L/Au:N/C:N/I:P/A:P |
Classification
- Weakness
-
- CWE-310 Cryptographic Issues
- Technology feeds
References
-
vupen.com
/english/advisories/2009/2420
vdb-entry, vendor-advisory
-
secunia.com
/advisories/36417
third-party-advisory, vendor-advisory
-
code.google.com
/p/chromium/issues/detail?id=18725
vendor-advisory
-
googlechromereleases.blogspot.com
/2009/08/stable-update-security-fixes.html
vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/52903
vdb-entry
Sources
- CVE List CVE-2009-2973
- NVD CVE-2009-2973
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Consolidate version ranges.