CVE-2012-2827
UnknownEPSS 0.64%
Last modified
CVE-2012-2827 is a vulnerability of currently unknown severity. Use-after-free vulnerability in the UI in Google Chrome before 20.0.1132.43 on Mac OS X allows attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors.. EPSS estimates a 0.64% chance of exploitation in the next 30 days.
Description
Use-after-free vulnerability in the UI in Google Chrome before 20.0.1132.43 on Mac OS X allows attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Chrome | <= 20.0.1132.42 | |
| Chrome | 20.0.1132.0 | |
| Chrome | 20.0.1132.1 | |
| Chrome | 20.0.1132.2 | |
| Chrome | 20.0.1132.3 | |
| Chrome | 20.0.1132.4 | |
| Chrome | 20.0.1132.5 | |
| Chrome | 20.0.1132.6 | |
| Chrome | 20.0.1132.7 | |
| Chrome | 20.0.1132.8 | |
| Chrome | 20.0.1132.9 | |
| Chrome | 20.0.1132.10 | |
| Chrome | 20.0.1132.11 | |
| Chrome | 20.0.1132.12 | |
| Chrome | 20.0.1132.13 | |
| Chrome | 20.0.1132.14 | |
| Chrome | 20.0.1132.15 | |
| Chrome | 20.0.1132.16 | |
| Chrome | 20.0.1132.17 | |
| Chrome | 20.0.1132.18 | |
| Chrome | 20.0.1132.19 | |
| Chrome | 20.0.1132.20 | |
| Chrome | 20.0.1132.21 | |
| Chrome | 20.0.1132.22 | |
| Chrome | 20.0.1132.23 | |
| Chrome | 20.0.1132.24 | |
| Chrome | 20.0.1132.25 | |
| Chrome | 20.0.1132.26 | |
| Chrome | 20.0.1132.27 | |
| Chrome | 20.0.1132.28 | |
| Chrome | 20.0.1132.29 | |
| Chrome | 20.0.1132.30 | |
| Chrome | 20.0.1132.31 | |
| Chrome | 20.0.1132.32 | |
| Chrome | 20.0.1132.33 | |
| Chrome | 20.0.1132.34 | |
| Chrome | 20.0.1132.35 | |
| Chrome | 20.0.1132.36 | |
| Chrome | 20.0.1132.37 | |
| Chrome | 20.0.1132.38 | |
| Chrome | 20.0.1132.39 | |
| Chrome | 20.0.1132.40 | |
| Chrome | 20.0.1132.41 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2012-2827?
Use-after-free vulnerability in the UI in Google Chrome before 20.0.1132.43 on Mac OS X allows attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors.
How severe is CVE-2012-2827?
Severity scoring for CVE-2012-2827 is pending analysis. The EPSS model estimates a 0.64% probability of exploitation in the next 30 days.
How do I fix CVE-2012-2827?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2012
- CVE-2012-2821The autofill implementation in Google Chrome before 20.0.113…
- CVE-2012-2822The PDF functionality in Google Chrome before 20.0.1132.43 a…
- CVE-2012-2823Use-after-free vulnerability in Google Chrome before 20.0.11…
- CVE-2012-2824Use-after-free vulnerability in Google Chrome before 20.0.11…
- CVE-2012-2825The XSL implementation in Google Chrome before 20.0.1132.43 …
- CVE-2012-2826Google Chrome before 20.0.1132.43 does not properly implemen…
- CVE-2012-2828Multiple integer overflows in the PDF functionality in Googl…
- CVE-2012-2829Use-after-free vulnerability in the Cascading Style Sheets (…
- CVE-2012-2830Google Chrome before 20.0.1132.43 does not properly set arra…
- CVE-2012-2831Use-after-free vulnerability in Google Chrome before 20.0.11…
- CVE-2012-2832The image-codec implementation in the PDF functionality in G…
- CVE-2012-2833Buffer overflow in the JS API in the PDF functionality in Go…
Are you affected by CVE-2012-2827?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
