ChromeWeb browser · Google
CVE-2014-1733
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 · uneditedThe PointerCompare function in codegen.cc in Seccomp-BPF, as used in Google Chrome before 34.0.1847.131 on Windows and OS X and before 34.0.1847.132 on Linux, does not properly merge blocks, which might allow remote attackers to bypass intended sandbox restrictions by leveraging renderer access.
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 confidenceA logic flaw in Seccomp-BPF's PointerCompare function in codegen.cc causes improper block merging, allowing a remote attacker with renderer access to bypass Chrome's sandbox restrictions. This affects Chrome versions prior to 34.0.1847.131 (Windows/OS X) and 34.0.1847.132 (Linux).
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
ChromeWeb browser
< 34.0.1847.131< 34.0.1847.132CVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Check installed Chrome versionOpen chrome://version in the browser address bar and note the version number displayedAffected if Version is below 34.0.1847.131 on Windows/OS X, or below 34.0.1847.132 on Linux
-
Confirm Chrome version on Windows or OS XIf on Windows or OS X, compare the full version number to 34.0.1847.131Affected if Version string starts with a number less than 34.0.1847.131 on Windows/OS X
-
Confirm Chrome version on LinuxIf on Linux, compare the full version number to 34.0.1847.132Affected if Version string starts with a number less than 34.0.1847.132 on Linux
-
Verify Seccomp-BPF sandbox is in useCheck Chrome's sandbox status by navigating to chrome://sandbox or examining process arguments; on Linux, look for 'seccomp-bpf' in process infoAffected if Seccomp-BPF sandbox is enabled (this is the default on supported versions) and version is vulnerable
You are affected if Chrome version is below 34.0.1847.131 (Windows/OS X) or 34.0.1847.132 (Linux) and Seccomp-BPF sandbox is enabled.
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 data34.0.1847.13134.0.1847.132
Update Google Chrome to version 34.0.1847.131 or later on Windows/OS X, or 34.0.1847.132 or later on Linux, to resolve the improper block merging in the PointerCompare function.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-1733 — 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-2014-1733 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