Debian LinuxOperating system · Debian
CVE-2013-2861
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 · uneditedUse-after-free vulnerability in the SVG implementation in Google Chrome before 27.0.1453.110 allows remote attackers to cause a denial of service or possibly have unspecified other impact via unknown 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 confidenceUse-after-free memory corruption vulnerability in Google Chrome's SVG (Scalable Vector Graphics) rendering engine before version 27.0.1453.110. A remote attacker can exploit this by enticing a user to visit a malicious webpage containing crafted SVG content, causing the browser to access freed memory, leading to denial of service or potential arbitrary code execution.
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
Debian LinuxOperating system
= 7.0= 8.0
ChromeWeb browser
<= 27.0.1453.109= 27.0.1453.0= 27.0.1453.1= 27.0.1453.2= 27.0.1453.3= 27.0.1453.4= 27.0.1453.5= 27.0.1453.6= 27.0.1453.7= 27.0.1453.8= 27.0.1453.9= 27.0.1453.10CVSS 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.
-
Verify Chrome is installedCheck for Chrome executable: on Linux run 'which google-chrome' or 'which chromium-browser', on Windows check C:\Program Files\Google\Chrome\Application\chrome.exeAffected if Chrome is not installed on the system
-
Determine installed Chrome versionRun 'google-chrome --version' or 'chromium-browser --version' on Linux, or check Help > About Google Chrome on WindowsAffected if Version displayed is 27.0.1453.109 or earlier, or any of 27.0.1453.0 through 27.0.1453.10 specifically
-
Compare version against CVE rangeCompare your installed version to the affected range: versions <= 27.0.1453.109, including 27.0.1453.0 through 27.0.1453.10. The fixed version is 27.0.1453.110.Affected if Installed version falls within the affected range and is earlier than 27.0.1453.110
-
Check Debian package version (if applicable)On Debian systems, run 'dpkg -l | grep -i chrome' or 'apt-cache policy chromium' to check the installed package versionAffected if Running Debian 7.0 or 8.0 with an affected Chrome package version
You are affected if Google Chrome or Chromium is installed with a version at or below 27.0.1453.109, or any specific version from 27.0.1453.0 through 27.0.1453.10, on any OS including Debian 7.0 or 8.0.
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 dataUpgrade Google Chrome to version 27.0.1453.110 or later. Organizations should deploy browser updates through their standard patch management processes to ensure all users receive the patched version.
Fix this in Debian Linux
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-2861 — 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-2861 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