ChromeWeb browser · Google
CVE-2020-6525
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 · uneditedHeap buffer overflow in Skia in Google Chrome prior to 84.0.4147.89 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
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 confidenceHeap buffer overflow vulnerability in Skia's graphics rendering library that can be triggered remotely via malicious HTML pages, potentially allowing heap corruption and possible arbitrary code execution. The flaw exists in image processing code within Skia versions prior to the fix.
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
< 84.0.4147.89
Debian LinuxOperating system
= 10.0
FedoraOperating system
= 31= 32= 15.0= 15.1= 15.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
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 version on Windows or MacNavigate to chrome://settings/help or use 'Help > About Google Chrome' to view the installed version numberAffected if The version displayed is lower than 84.0.4147.89 (for example, 84.0.4147.80 or earlier)
-
Check Google Chrome version on LinuxRun 'google-chrome --version' or 'chromium --version' in a terminalAffected if The reported version is below 84.0.4147.89
-
Check if Skia library is installed on Debian 10Run 'dpkg -l | grep skia' or 'apt list --installed 2>/dev/null | grep -i skia' to list installed Skia packagesAffected if Skia library packages are installed from Debian 10 repositories and no security update has been applied
-
Check if Skia library is installed on Fedora 31 or 32Run 'rpm -qa | grep -i skia' or 'dnf list installed | grep -i skia' to list installed Skia packagesAffected if Skia library packages are installed from Fedora 31 or 32 repositories and remain unpatched
-
Check if Skia library is installed on openSUSE Leap 15.1/15.2 or Backports SLE 15Run 'rpm -qa | grep -i skia' or 'zypper se -i skia' to list installed Skia packagesAffected if Skia library packages are installed from the listed openSUSE versions and remain unpatched
You are affected if you are running Google Chrome below version 84.0.4147.89, or if you have a Skia library installed from the affected Debian 10, Fedora 31/32, openSUSE Leap 15.1/15.2, or openSUSE Backports SLE 15 repositories without security updates applied.
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 data84.0.4147.89
Update Google Chrome to version 84.0.4147.89 or later. If using Skia library independently in custom applications, update to the patched Skia version that addresses the heap overflow.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6525 — 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-2020-6525 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