Vulnerabilities · 2009 · Google
CVE-2009-2973
Google Chrome vulnerability
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 products
Chrome. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Google Chrome runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- code.google.com/p/chromium/issues/detail?id=18725 · Vendor Advisory
- googlechromereleases.blogspot.com/2009/08/stable-update-security-fixes.html · Vendor Advisory
- secunia.com/advisories/36417 · Vendor Advisory
- www.vupen.com/english/advisories/2009/2420 · Vendor Advisory
- exchange.xforce.ibmcloud.com/vulnerabilities/52903
- nvd.nist.gov/vuln/detail/CVE-2009-2973
- cve.org/CVERecord?id=CVE-2009-2973
More vulnerabilities in Google products
CVE-2026-28615CVE-2026-28587CVE-2026-28576CVE-2026-28575CVE-2026-20418CVE-2026-20417CVE-2026-20415CVE-2026-20414All 12,443
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.