Ubuntu LinuxOperating system · Canonical
CVE-2014-7943
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 40.0.2214.91, allows remote attackers to cause a denial of service (out-of-bounds read) 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 · high confidenceSkia graphics library, as used in Google Chrome before 40.0.2214.91, contains an out-of-bounds read vulnerability that allows remote attackers to cause a denial of service by reading memory outside allocated buffers via unspecified vectors.
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
Ubuntu LinuxOperating system
= 14.04= 14.10
Enterprise Linux Desktop SupplementaryOperating system
= 6.0
Enterprise Linux Server SupplementaryOperating system
= 6.0
Enterprise Linux Server Supplementary EusOperating system
= 6.6.z
Enterprise Linux Workstation SupplementaryOperating system
= 6.0
ChromeWeb browser
<= 40.0.2214.85= 13.1= 13.2= 40.0.2214.110CVSS 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 Google Chrome versionNavigate to chrome://settings/help or run 'google-chrome --version' in terminal to see the installed Chrome versionAffected if Version is 40.0.2214.85 or lower
-
Check Chromium versionRun 'chromium --version' or 'chromium-browser --version' in terminalAffected if Version is 40.0.2214.110 (the listed vulnerable version)
-
Verify Ubuntu releaseRun 'lsb_release -a' or check /etc/lsb-releaseAffected if Release is 14.04 or 14.10 and Chrome/Chromium is installed
-
Verify Red Hat Enterprise Linux versionRun 'cat /etc/redhat-release'Affected if Version shows 6.0, 6.6, or 6.z variant with supplementary repositories enabled
-
Verify openSUSE versionRun 'cat /etc/os-release' or 'lsb_release -a'Affected if Version is 13.1 or 13.2 and Chrome/Chromium is installed
-
Confirm Skia library presenceCheck if Chrome/Chromium is bundled with libskia (common path: /opt/google/chrome/lib/libskia.so or within the browser's resources)Affected if Skia library exists in the Chrome/Chromium installation directory
A user is affected if they are running Google Chrome version 40.0.2214.85 or lower, or Chromium version 40.0.2214.110, on Ubuntu 14.04/14.10, RHEL 6.x, or openSUSE 13.1/13.2.
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 40.0.2214.91 or later to patch the vulnerability in the bundled Skia library.
Fix this in Ubuntu Linux
Scoped from the published advisory
- Consultation1.0 h
- Implementation0.5 h
- Testing1.0 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-2014-7943 — 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-7943 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