LiveActive security incident?Get immediate response
CVE Record

CVE-2012-1846: Google Chrome 17.0.963.66 and earlier allows remote attackers to bypass the sandbox protection mechanism by...

Google Chrome 17.0.963.66 and earlier allows remote attackers to bypass the sandbox protection mechanism by leveraging access to a sandboxed process, as demonstrated by VUPEN during a Pwn2Own competition at CanSecWest 2012. NOTE: the primary affected product may be clarified later; it was not identified by the researcher, who reportedly stated "it really doesn't matter if it's third-party code."

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This CVE describes a Google Chrome sandbox bypass affecting Chrome 17.0.963.66 and earlier. A sandbox bypass can reduce the browser’s containment protections after an attacker already has code running in a sandboxed process. The public record is old and sparse, and it does not identify a current patch advisory in the provided sources. Exposure is most plausible on unmanaged or legacy systems still running Chrome 17.0.963.66 or earlier. Modern managed browser fleets are unlikely to be affected, but this should be verified rather than assumed, especially on kiosks, lab systems, and old virtual desktops. Do not treat this as a current emergency without evidence of legacy exposure. Prioritize it as a hygiene and asset-management check: old browsers are high-risk technology debt, but the provided sources do not show active exploitation or current widespread exposure. Mitigation focus: Inventory endpoints for Chrome 17.0.963.66 and earlier.; Remove or replace unsupported Chrome versions where found.; Check Google or vendor guidance for the relevant Chrome release lineage..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2012-1846 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.