CVE-2010-3253
UnknownEPSS 0.91%
Last modified
CVE-2010-3253 is a vulnerability of currently unknown severity. The implementation of notification permissions in Google Chrome before 6.0.472.53 allows attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via unknown vectors.. EPSS estimates a 0.91% chance of exploitation in the next 30 days.
Description
The implementation of notification permissions in Google Chrome before 6.0.472.53 allows attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via unknown vectors.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Chrome | < 6.0.472.53 |
References
- http://code.google.com/p/chromium/issues/detail?id=50839Exploit, Issue Tracking, Patch, Vendor Advisory
- http://code.google.com/p/chromium/issues/detail?id=50839Exploit, Issue Tracking, Patch, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2010-3253?
The implementation of notification permissions in Google Chrome before 6.0.472.53 allows attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via unknown vectors.
How severe is CVE-2010-3253?
Severity scoring for CVE-2010-3253 is pending analysis. The EPSS model estimates a 0.91% probability of exploitation in the next 30 days.
How do I fix CVE-2010-3253?
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 2010
- CVE-2010-3247Google Chrome before 6.0.472.53 does not properly restrict t…
- CVE-2010-3248Google Chrome before 6.0.472.53 does not properly restrict c…
- CVE-2010-3249Google Chrome before 6.0.472.53 does not properly implement …
- CVE-2010-3250Unspecified vulnerability in Google Chrome before 6.0.472.53…
- CVE-2010-3251The WebSockets implementation in Google Chrome before 6.0.47…
- CVE-2010-3252Use-after-free vulnerability in the Notifications presenter …
- CVE-2010-3254The WebSockets implementation in Google Chrome before 6.0.47…
- CVE-2010-3255Google Chrome before 6.0.472.53 and webkitgtk before 1.2.6 d…
- CVE-2010-3256Google Chrome before 6.0.472.53 does not properly limit the …
- CVE-2010-3257Use-after-free vulnerability in WebKit, as used in Apple Saf…
- CVE-2010-3258The sandbox implementation in Google Chrome before 6.0.472.5…
- CVE-2010-3259WebKit, as used in Apple Safari before 4.1.3 and 5.0.x befor…
Are you affected by CVE-2010-3253?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
