ChromeWeb browser · Google
CVE-2013-0883
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 · uneditedSkia, as used in Google Chrome before 25.0.1364.97 on Windows and Linux, and before 25.0.1364.99 on Mac OS X, allows remote attackers to cause a denial of service (incorrect read operation) via unspecified vectors.
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 confidenceA vulnerability in the Skia graphics library, used by Google Chrome, allows remote attackers to cause a denial of service through an incorrect memory read operation. The issue affects Chrome versions prior to 25.0.1364.97 on Windows and Linux, and prior to 25.0.1364.99 on Mac OS X.
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
< 25.0.1364.97< 25.0.1364.99= 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.
-
Identify the operating systemRun 'uname -s' on Linux/Mac or check System Properties on Windows to determine if the system is Windows, Linux, or Mac OS X.Affected if The OS is Windows, Linux, or Mac OS X (any of the three platforms affected by this CVE)
-
Check installed Google Chrome version on WindowsNavigate to Chrome settings, click 'About Google Chrome', or run the command '"C:\Program Files\Google\Chrome\Application\chrome.exe" --version' in Command Prompt.Affected if The displayed version is lower than 25.0.1364.97
-
Check installed Google Chrome version on LinuxRun 'google-chrome --version' or 'chromium --version' in the terminal.Affected if The displayed version is lower than 25.0.1364.97
-
Check installed Google Chrome version on Mac OS XRun '/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version' in Terminal, or click Chrome > About Google Chrome from the menu bar.Affected if The displayed version is lower than 25.0.1364.99
-
Check Opensuse version (if applicable)Run 'cat /etc/osrelease' or 'lsb_release -a' to identify the Opensuse version.Affected if The system runs Opensuse 12.1 or 12.2 with an affected Chrome installation
A user is affected if they are running Google Chrome version 25.0.1364.96 or lower on Windows/Linux, or 25.0.1364.98 or lower on Mac OS X, particularly on Opensuse 12.1 or 12.2 systems.
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 data25.0.1364.9725.0.1364.99
Update Google Chrome to version 25.0.1364.97 or later (Windows/Linux) or 25.0.1364.99 or later (Mac OS X) to incorporate the patched Skia library.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0883 — 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-0883 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