CVE-2009-2973
N/A
Published: August 27, 2009 at 05:00 PM UTC
Updated: June 16, 2026 at 11:10 PM UTC
1 product affected across 1 vendorChrome
Using N/A by N/A?
Get instant alerts when new vulnerabilities affect N/A - before attackers find them.
Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.9%
Description
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.
Affected
Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.
Remediation
No guide yetNo remediation guidance has been written for this CVE yet. What the record does show:
References (5)
x_refsource_CONFIRMVendor Advisory
Source: [email protected]
http://code.google.com/p/chromium/issues/detail?id=18725x_refsource_CONFIRMVendor Advisory
Source: [email protected]
http://googlechromereleases.blogspot.com/2009/08/stable-update-security-fixes.htmlThird Party Advisoryx_refsource_SECUNIAVendor Advisory
Source: [email protected]
http://secunia.com/advisories/36417VDB Entryx_refsource_VUPENVendor Advisory
Source: [email protected]
http://www.vupen.com/english/advisories/2009/2420VDB Entryx_refsource_XF
Source: [email protected]
https://exchange.xforce.ibmcloud.com/vulnerabilities/52903Quick Info
StatusMODIFIED
CWE
CWE-310
Get alerted
Stop reading CVE feeds looking for your own stack
Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.
Free plan, no card