CVE-2013-2879
Last modified
CVE-2013-2879 is a vulnerability of currently unknown severity. Google Chrome before 28.0.1500.71 does not properly determine the circumstances in which a renderer process can be considered a trusted process for sign-in and subsequent sync operations, which makes it easier for remote attackers to conduct phishing attacks via a crafted web site.. EPSS estimates a 0.92% chance of exploitation in the next 30 days.
Description
Google Chrome before 28.0.1500.71 does not properly determine the circumstances in which a renderer process can be considered a trusted process for sign-in and subsequent sync operations, which makes it easier for remote attackers to conduct phishing attacks via a crafted web site.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Chrome | <= 28.0.1500.70 | |
| Chrome | 28.0.1500.0 | |
| Chrome | 28.0.1500.2 | |
| Chrome | 28.0.1500.3 | |
| Chrome | 28.0.1500.4 | |
| Chrome | 28.0.1500.5 | |
| Chrome | 28.0.1500.6 | |
| Chrome | 28.0.1500.8 | |
| Chrome | 28.0.1500.9 | |
| Chrome | 28.0.1500.10 | |
| Chrome | 28.0.1500.11 | |
| Chrome | 28.0.1500.12 | |
| Chrome | 28.0.1500.13 | |
| Chrome | 28.0.1500.14 | |
| Chrome | 28.0.1500.15 | |
| Chrome | 28.0.1500.16 | |
| Chrome | 28.0.1500.17 | |
| Chrome | 28.0.1500.18 | |
| Chrome | 28.0.1500.19 | |
| Chrome | 28.0.1500.20 | |
| Chrome | 28.0.1500.21 | |
| Chrome | 28.0.1500.22 | |
| Chrome | 28.0.1500.23 | |
| Chrome | 28.0.1500.24 | |
| Chrome | 28.0.1500.25 | |
| Chrome | 28.0.1500.26 | |
| Chrome | 28.0.1500.27 | |
| Chrome | 28.0.1500.28 | |
| Chrome | 28.0.1500.29 | |
| Chrome | 28.0.1500.31 | |
| Chrome | 28.0.1500.32 | |
| Chrome | 28.0.1500.33 | |
| Chrome | 28.0.1500.34 | |
| Chrome | 28.0.1500.35 | |
| Chrome | 28.0.1500.36 | |
| Chrome | 28.0.1500.37 | |
| Chrome | 28.0.1500.38 | |
| Chrome | 28.0.1500.39 | |
| Chrome | 28.0.1500.40 | |
| Chrome | 28.0.1500.41 | |
| Chrome | 28.0.1500.42 | |
| Chrome | 28.0.1500.43 | |
| Chrome | 28.0.1500.44 | |
| Chrome | 28.0.1500.45 | |
| Chrome | 28.0.1500.46 | |
| Chrome | 28.0.1500.47 | |
| Chrome | 28.0.1500.48 | |
| Chrome | 28.0.1500.49 | |
| Chrome | 28.0.1500.50 | |
| Chrome | 28.0.1500.51 |
Showing 50 of 64 affected configurations. See NVD for the full list.
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2013-2879?
How severe is CVE-2013-2879?
How do I fix CVE-2013-2879?
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 2013
- CVE-2013-2873Use-after-free vulnerability in Google Chrome before 28.0.15…
- CVE-2013-2874Google Chrome before 28.0.1500.71 on Windows, when an Nvidia…
- CVE-2013-2875core/rendering/svg/SVGInlineTextBox.cpp in the SVG implement…
- CVE-2013-2876browser/extensions/api/tabs/tabs_api.cc in Google Chrome bef…
- CVE-2013-2877parser.c in libxml2 before 2.9.0, as used in Google Chrome b…
- CVE-2013-2878Google Chrome before 28.0.1500.71 allows remote attackers to…
- CVE-2013-2880Multiple unspecified vulnerabilities in Google Chrome before…
- CVE-2013-2881Google Chrome before 28.0.1500.95 does not properly handle f…
- CVE-2013-2882Google V8, as used in Google Chrome before 28.0.1500.95, all…
- CVE-2013-2883Use-after-free vulnerability in Google Chrome before 28.0.15…
- CVE-2013-2884Use-after-free vulnerability in the DOM implementation in Go…
- CVE-2013-2885Use-after-free vulnerability in Google Chrome before 28.0.15…
Are you affected by CVE-2013-2879?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
