ChromeWeb browser · Google
CVE-2024-1283
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 121.0.6167.160 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
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 graphics library used by Google Chrome. A remote attacker can exploit this by tricking a user into visiting a crafted HTML page, potentially leading to heap corruption and possible 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
ChromeWeb browser
< 121.0.6167.160
FedoraOperating system
= 38= 39CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 your systemOpen Chrome and navigate to chrome://version, or on Windows check Help > About Google Chrome, or run 'google-chrome --version' in terminalAffected if The displayed version is lower than 121.0.6167.160
-
Verify Chrome version on Linux systemsRun the command 'google-chrome --version' or '/opt/google/chrome/google-chrome --version' in a terminalAffected if The reported version number is less than 121.0.6167.160
-
Check Skia graphics library package on FedoraRun 'rpm -qa | grep -i skia' to list installed skia packages, then run 'rpm -q --changelog skia' or check the package version with 'rpm -q skia'Affected if You are running Fedora 38 or 39 and the skia library is installed (the vulnerability exists in the Skia library used by Chrome on these Fedora versions)
-
Confirm Chrome is actually in useCheck if Google Chrome browser is the default browser or has been recently launched on the affected systemAffected if Google Chrome is installed and used on a Windows, Mac, Linux, or Fedora system with a version below 121.0.6167.160
You are affected if you are running Google Chrome with a version lower than 121.0.6167.160 on any platform, or running Google Chrome on Fedora 38 or 39 systems, because the heap buffer overflow in the Skia graphics library can be triggered by visiting a crafted HTML page.
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.
dbcve · scoped121.0.6167.160
Update Google Chrome to version 121.0.6167.160 or later to patch the vulnerability.
Chrome 121.0.6167.160 (or later stable release)
- For Google Chrome desktop users: Navigate to Chrome menu > Help > About Google Chrome and verify version is 121.0.6167.160 or later; if not, click 'Update Google Chrome' to install the latest version
- For Fedora systems: Run 'sudo dnf update google-chrome-stable' to fetch and apply the patched Chrome package
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1283 — 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-2024-1283 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