CVE-2009-2556
UnknownEPSS 1.58%
Last modified
CVE-2009-2556 is a vulnerability of currently unknown severity. Google Chrome before 2.0.172.37 allows attackers to leverage renderer access to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via unspecified vectors that trigger excessive memory allocation.. EPSS estimates a 1.58% chance of exploitation in the next 30 days.
Description
Google Chrome before 2.0.172.37 allows attackers to leverage renderer access to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via unspecified vectors that trigger excessive memory allocation.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Chrome | <= 2.0.172.33 | |
| Chrome | 0.2.149.29 | |
| Chrome | 0.2.149.30 | |
| Chrome | 0.2.152.1 | |
| Chrome | 0.2.153.1 | |
| Chrome | 0.3.154.0 | |
| Chrome | 0.3.154.3 | |
| Chrome | 0.4.154.18 | |
| Chrome | 0.4.154.22 | |
| Chrome | 0.4.154.31 | |
| Chrome | 0.4.154.33 | |
| Chrome | 1.0.154.36 | |
| Chrome | 1.0.154.39 | |
| Chrome | 1.0.154.42 | |
| Chrome | 1.0.154.43 | |
| Chrome | 1.0.154.46 | |
| Chrome | 1.0.154.48 | |
| Chrome | 1.0.154.52 | |
| Chrome | 1.0.154.53 | |
| Chrome | 1.0.154.59 | |
| Chrome | 2.0.156.1 | |
| Chrome | 2.0.157.0 | |
| Chrome | 2.0.157.2 | |
| Chrome | 2.0.158.0 | |
| Chrome | 2.0.159.0 | |
| Chrome | 2.0.172 | |
| Chrome | 2.0.172.30 | |
| Chrome | 2.0.172.31 |
References
- http://secunia.com/advisories/35844Vendor Advisory
- http://www.vupen.com/english/advisories/2009/1924Vendor Advisory
- http://secunia.com/advisories/35844Vendor Advisory
- http://www.vupen.com/english/advisories/2009/1924Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2009-2556?
Google Chrome before 2.0.172.37 allows attackers to leverage renderer access to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via unspecified vectors that trigger excessive memory allocation.
How severe is CVE-2009-2556?
Severity scoring for CVE-2009-2556 is pending analysis. The EPSS model estimates a 1.58% probability of exploitation in the next 30 days.
How do I fix CVE-2009-2556?
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 2009
- CVE-2009-2550Stack-based buffer overflow in Hamster Audio Player 0.3a all…
- CVE-2009-2551Multiple cross-site scripting (XSS) vulnerabilities in Scrip…
- CVE-2009-2552Multiple directory traversal vulnerabilities in comments.php…
- CVE-2009-2553Multiple SQL injection vulnerabilities in comments.php in Su…
- CVE-2009-2554SQL injection vulnerability in the search method in jobline.…
- CVE-2009-2555Heap-based buffer overflow in src/jsregexp.cc in Google V8 b…
- CVE-2009-2557Directory traversal vulnerability in system/download.php in …
- CVE-2009-2558system/message.php in Admin News Tools 2.5 does not properly…
- CVE-2009-2559Buffer overflow in the IPMI dissector in Wireshark 1.2.0 all…
- CVE-2009-2560Multiple unspecified vulnerabilities in Wireshark 1.2.0 allo…
- CVE-2009-2561Unspecified vulnerability in the sFlow dissector in Wireshar…
- CVE-2009-2562Unspecified vulnerability in the AFS dissector in Wireshark …
Are you affected by CVE-2009-2556?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST