CVE-2023-28885
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 · uneditedThe MyLink infotainment system (build 2021.3.26) in General Motors Chevrolet Equinox 2021 vehicles allows attackers to cause a denial of service (temporary failure of Media Player functionality) via a crafted MP3 file.
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 confidenceThe MyLink infotainment system (build 2021.3.26) in Chevrolet Equinox 2021 vehicles contains a media parsing vulnerability where specially crafted MP3 files cause the Media Player to fail, resulting in temporary denial of service. The vulnerability likely stems from insufficient input validation or improper handling of malformed audio file metadata within the infotainment software.
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= 2021.3.26CVSS 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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/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.
-
Identify the infotainment systemNavigate to the vehicle's infotainment settings or check the vehicle documentation to confirm the system is GM MyLink Infotainment System. This is typically displayed in the system info or about section of the infotainment menu.Affected if The vehicle does not have MyLink, the vulnerability does not apply.
-
Check the MyLink firmware versionAccess the MyLink system settings, usually found under Settings > About or System Information. Look for the build/version number displayed as '2021.3.26' or similar.Affected if The version is exactly 2021.3.26 - this is the only affected version. Other versions are not affected.
-
Verify media player functionalityConfirm the Media Player or Audio source selection feature is accessible and operational on the infotainment system. Attempt to access the MP3/media playback option.Affected if The media player feature must be present and usable for the vulnerability to be triggerable.
You are affected only if your vehicle has MyLink infotainment system with firmware version exactly 2021.3.26 and the media player feature is accessible.
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 dataUsers should avoid playing MP3 files from untrusted or unknown sources. The vendor (GM) must issue a firmware update that properly validates MP3 file structures before processing. Until an official patch is available, vehicle owners should be cautious with media files from external sources.
- Consultation8.0 h
- Implementation40.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $20,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28885 — 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-2023-28885 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