ChromeWeb browser · Google
CVE-2024-1077
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 · uneditedUse after free in Network in Google Chrome prior to 121.0.6167.139 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 confidenceUse-after-free vulnerability in Google Chrome's Network component prior to version 121.0.6167.139 allows a remote attacker to potentially exploit heap corruption via a malicious file, leading to 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.139
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
- 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 installed Google Chrome versionOpen Chrome, click the three-dot menu, select 'Help' then 'About Google Chrome'. Alternatively, navigate to chrome://settings/help in the address bar. Note the version number displayed.Affected if The displayed version is lower than 121.0.6167.139 (e.g., 121.0.6167.85, 120.0.6099.109, etc.)
-
Check Chrome version via command lineRun 'google-chrome --version' or 'google-chrome-stable --version' in a terminal to retrieve the installed Chrome version.Affected if The version output is less than 121.0.6167.139 (e.g., shows 121.0.6167.85 or earlier)
-
Verify Fedora OS version if applicableRun 'cat /etc/fedora-release' or 'fedora-release' command to determine the Fedora version number.Affected if The system runs Fedora 38 or Fedora 39 AND Google Chrome version is below 121.0.6167.139
You are affected if you are running any version of Google Chrome prior to 121.0.6167.139, particularly on Fedora 38 or 39 systems.
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.139
Update Google Chrome to version 121.0.6167.139 or later to address the use-after-free vulnerability in the Network component.
Chrome 121.0.6167.139 or later
- For Chrome Desktop users: Open Chrome, go to Settings > Help > About Google Chrome, and click 'Update Chrome' to upgrade to version 121.0.6167.139 or later
- Alternatively, download the latest Chrome version from the official Google Chrome website: https://www.google.com/chrome/
- For Fedora systems: Run 'sudo dnf update google-chrome-stable' to apply the security update
Generated from the published advisory — verify against the referenced sources before acting.
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-2024-1077 — 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-1077 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