dbcve.org
ChromeWeb browser · Google

CVE-2015-1360

HIGH · 7.5 CVSS v2.0 Published 2015-01-27
Fix available
A fix is available. Upgrade to after 40.0.2214.85 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Skia, as used in Google Chrome before 40.0.2214.91, allows remote attackers to cause a denial of service (buffer over-read) or possibly have unspecified other impact via crafted data that is improperly handled during text drawing, related to gpu/GrBitmapTextContext.cpp and gpu/GrDistanceFieldTextContext.cpp, a different vulnerability than CVE-2015-1205.

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 confidence

A buffer over-read vulnerability in Skia's GPU text rendering code (GrBitmapTextContext.cpp and GrDistanceFieldTextContext.cpp) allows remote attackers to cause denial of service or possibly achieve unspecified impact by providing crafted data during text drawing operations in Google Chrome before version 40.0.2214.91.

MitigationUpdate Google Chrome to version 40.0.2214.91 or later, or update the Skia library to a patched version if used in other applications.

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
Affected:<= 40.0.2214.85

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Chrome version
    Navigate to chrome://settings/help or click Help > About Google Chrome to view the current version number
    Affected if Version is 40.0.2214.85 or lower (the version number shown is less than 40.0.2214.91)
  2. Verify GPU acceleration is enabled
    Navigate to chrome://gpu and look for 'GPU rasterization' or 'GPU rendering' status. Also check chrome://flags for 'Enable GPU rasterization' flag
    Affected if GPU acceleration/rasterization is enabled - the vulnerability resides in the GPU text rendering path (GrBitmapTextContext.cpp and GrDistanceFieldTextContext.cpp)
  3. Confirm text rendering uses GPU backend
    The vulnerable code is in Skia's GPU text rendering context. On systems with discrete GPUs or when hardware acceleration is active, Chrome uses the GPU path for text rendering
    Affected if Hardware acceleration is enabled and Chrome is using the GPU-accelerated rendering pipeline for text

You are affected if your Chrome version is 40.0.2214.85 or lower AND GPU/hardware acceleration for text rendering is enabled in your browser settings.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 40.0.2214.85
Interim mitigation

Update Google Chrome to version 40.0.2214.91 or later, or update the Skia library to a patched version if used in other applications.

Fix this in Chrome Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-1360 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-1360 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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