Debian LinuxOperating system · Debian
CVE-2024-0808
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 · uneditedInteger underflow in WebUI in Google Chrome prior to 121.0.6167.85 allowed a remote attacker to potentially exploit heap corruption via a malicious file. (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 confidenceInteger underflow vulnerability in Google Chrome's WebUI component prior to version 121.0.6167.85 allows a remote attacker to exploit heap corruption via a malicious file, leading to 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
= 11.0
ChromeWeb browser
< 121.0.6167.85
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.
-
Verify Google Chrome is installedRun 'google-chrome --version' or 'google-chrome-stable --version' in terminal, or check for Chrome in your system package managerAffected if Google Chrome is present on the system
-
Identify installed Chrome versionExecute 'google-chrome --version' or 'google-chrome-stable --version' and note the full version stringAffected if The version output is lower than 121.0.6167.85
-
Confirm Chrome release channelCheck if running stable, beta, or dev channel via 'google-chrome --version' output or about://chrome pageAffected if Running a stable channel version prior to 121.0.6167.85
-
Verify WebUI component is reachableOpen Chrome and navigate to any chrome:// URL (e.g., chrome://settings) to confirm WebUI subsystem loadsAffected if WebUI component is accessible in the browser environment
A user is affected if Google Chrome is installed with a version lower than 121.0.6167.85 and the WebUI component is functional.
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.85
Update Google Chrome to version 121.0.6167.85 or later to patch the integer underflow vulnerability.
Chrome 121.0.6167.85 or later (chromium-browser 121.0.6167.85+ on Linux distributions)
- Check current Google Chrome version by navigating to chrome://version in the browser address bar
- If the installed version is earlier than 121.0.6167.85, update Google Chrome to the latest available version
- For Debian 11.0 systems: run 'sudo apt-get update && sudo apt-get upgrade' to apply security updates for the chromium package
- For Fedora 38/39 systems: run 'sudo dnf update' to apply security updates for the chromium package
- Restart the browser after updating to ensure the patch is fully applied
- Verify the version is now 121.0.6167.85 or later by checking chrome://version again
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0808 — 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-0808 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