Chrome OsOperating system · Google
CVE-2013-2835
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGoogle Chrome OS before 26.0.1410.57 does not properly enforce origin restrictions for the O3D and Google Talk plug-ins, which allows remote attackers to bypass the domain-whitelist protection mechanism via a crafted web site, a different vulnerability than CVE-2013-2834.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceGoogle Chrome OS before 26.0.1410.57 fails to properly enforce origin restrictions for the O3D and Google Talk plugins, allowing a crafted website to bypass the domain-whitelist protection mechanism. This is a same-origin policy bypass specific to these NPAPI plugins.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Chrome OsOperating system
<= 26.0.1410.56= 26.0.1410.0= 26.0.1410.1= 26.0.1410.3= 26.0.1410.4= 26.0.1410.5= 26.0.1410.6= 26.0.1410.7= 26.0.1410.8= 26.0.1410.9= 26.0.1410.10= 26.0.1410.11CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm you are running Google Chrome OSCheck the OS type - this vulnerability only affects Chrome OS, not standard Chrome browser on other OSes. Look for Chrome OS in your system information or about chrome page.Affected if System is not Google Chrome OS (vulnerability does not apply)
-
Check the Chrome OS versionNavigate to chrome://settings or about:version in Chrome browser on Chrome OS to view the OS version. Compare against the affected versions: any version <= 26.0.1410.56 is vulnerable.Affected if Chrome OS version is 26.0.1410.56 or lower, or matches any of these: 26.0.1410.0 through 26.0.1410.11
-
Determine if O3D plugin is enabledNavigate to chrome://plugins in Chrome OS browser, look for the O3D plugin in the list. Check if it is set to 'Enabled' or 'Always allowed to run'.Affected if O3D plugin is enabled or set to always run (vulnerability requires at least one affected plugin to be enabled)
-
Determine if Google Talk plugin is enabledNavigate to chrome://plugins in Chrome OS browser, look for the Google Talk plugin in the list. Check if it is set to 'Enabled' or 'Always allowed to run'.Affected if Google Talk plugin is enabled or set to always run (vulnerability requires at least one affected plugin to be enabled)
User is affected only if running Chrome OS version 26.0.1410.56 or lower AND has either the O3D or Google Talk plugin enabled in the browser settings.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate Chrome OS to version 26.0.1410.57 or later. As a temporary workaround, consider disabling the O3D and Google Talk plugins in browser settings until the update can be applied.
Fix this in Chrome Os
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2835 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-2835 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data