ChromeWeb browser · Google
CVE-2013-0833
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 before 24.0.1312.52 allows remote attackers to cause a denial of service (out-of-bounds read) via vectors related to printing.
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 · moderate confidenceOut-of-bounds read vulnerability in Google Chrome's printing functionality that allows remote attackers to cause a denial of service via crafted print-related vectors in versions prior to 24.0.1312.52.
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
<= 24.0.1312.51= 24.0.1272.0= 24.0.1272.1= 24.0.1273.0= 24.0.1274.0= 24.0.1275.0= 24.0.1276.0= 24.0.1276.1= 24.0.1277.0= 24.0.1278.0= 24.0.1279.0= 24.0.1280.0= 12.1= 12.2CVSS 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
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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 if Google Chrome is installedOn Windows: Look for Chrome in Program Files or check Start menu. On Linux: Run 'which google-chrome' or check package manager. On Mac: Look in /Applications for Google Chrome.appAffected if Google Chrome is installed on the system
-
Determine installed Chrome versionOpen Chrome, click the menu icon, select Help > About Google Chrome, or navigate to chrome://settings/help. Alternatively, run 'google-chrome --version' from command line on Linux/MacAffected if The displayed version is 24.0.1312.51 or lower, or matches any of these: 24.0.1272.0, 24.0.1272.1, 24.0.1273.0, 24.0.1274.0, 24.0.1275.0, 24.0.1276.0, 24.0.1276.1, 24.0.1277.0, 24.0.1278.0, 24.0.1279.0, 24.0.1280.0
-
Check OpenSUSE package version (if Linux)Run 'rpm -qa | grep -i chrome' or 'zypper se google-chrome' to list the installed Chrome package versionAffected if The installed Chrome package version matches the affected versions listed above for OpenSUSE 12.1 or 12.2
-
Determine if printing feature is usedThe vulnerability is triggered through the printing functionality. Check if users have printed documents or if print dialogs have been accessed. On Linux, also check if CUPS print service is running and if Chrome printing module is loadedAffected if The Chrome browser is used to access printing functionality on a regular basis
You are affected if you have Google Chrome version 24.0.1312.51 or lower, or any of the specific 24.0.1272.x through 24.0.1280.0 versions installed, and you use the printing feature.
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 Google Chrome to version 24.0.1312.52 or later to patch the vulnerability.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing0.5 h
- Review / QA0.5 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0833 — 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-0833 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