Vulnerabilities · 2012 · Google
CVE-2012-4930
Google Chrome vulnerability
The SPDY protocol 3 and earlier, as used in Mozilla Firefox, Google Chrome, and other products, can perform TLS encryption of compressed data without properly obfuscating the length of the unencrypted data, which allows man-in-the-middle attackers to obtain plaintext HTTP headers by observing length differences during a series of guesses in which a string in an HTTP request potentially matches an unknown string in an HTTP header, aka a "CRIME" attack.
Affected products
Chrome, Firefox. 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
- arstechnica.com/security/2012/09/crime-hijacks-https-sessions/
- isecpartners.com/blog/2012/9/14/details-on-the-crime-attack.html
- lists.opensuse.org/opensuse-security-announce/2012-10/msg00010.html
- threatpost.com/en_us/blogs/crime-attack-uses-compression-ratio-tls-requests-side-channel-h
- www.ekoparty.org/2012/thai-duong.php
- www.iacr.org/cryptodb/data/paper.php?pubkey=3091
- www.theregister.co.uk/2012/09/14/crime_tls_attack/
- bugzilla.redhat.com/show_bug.cgi?id=857737
- nvd.nist.gov/vuln/detail/CVE-2012-4930
- cve.org/CVERecord?id=CVE-2012-4930
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.