ChromeWeb browser · Google
CVE-2022-2587
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 · uneditedOut of bounds write in Chrome OS Audio Server in Google Chrome on Chrome OS prior to 102.0.5005.125 allowed a remote attacker to potentially exploit heap corruption via crafted audio metadata.
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 confidenceAn out-of-bounds write vulnerability exists in the Chrome OS Audio Server component of Google Chrome on Chrome OS versions prior to 102.0.5005.125. A remote attacker can exploit this by sending crafted audio metadata, causing heap corruption and potentially achieving 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
ChromeWeb browser
< 102.0.5005.125CVSS 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 installed Chrome version on Chrome OSOpen Chrome browser, click the three-dot menu > Help > About Google Chrome. Alternatively, navigate to chrome://version in the address bar.Affected if The displayed version number is lower than 102.0.5005.125 (e.g., 102.0.5005.124, 101.x.x.x, etc.)
-
Confirm Chrome OS is the running platformCheck the operating system by looking at the login screen or system settings. Chrome OS devices typically show 'Chrome OS' as the OS in system information.Affected if The device is running Chrome OS and the Chrome version is below 102.0.5005.125
-
Verify Chrome browser is actively in useOpen the Chrome browser on the Chrome OS device. The Audio Server component runs as part of the Chrome process when the browser is active.Affected if Chrome is running or has been recently used on an affected Chrome OS version
A user is affected if Google Chrome on Chrome OS is installed with a version number less than 102.0.5005.125, as this is the specific version range and platform where the out-of-bounds write in the Audio Server component exists.
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 · scoped102.0.5005.125
Update Google Chrome on Chrome OS to version 102.0.5005.125 or later to remediate this vulnerability.
Chrome 102.0.5005.125 or later (stable release)
- Open Google Chrome and navigate to Settings > About Chrome (or visit chrome://settings/help)
- Chrome will automatically check for updates
- If version 102.0.5005.125 or later is available, click 'Update Chrome'
- Restart the browser to apply the update
- Verify the update by returning to About Chrome and confirming the version number
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-2022-2587 — 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-2022-2587 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