# CVE-2023-28885: Memory corruption in n/a

> Attackers can cause a temporary denial of service in the Media Player functionality of Chevrolet Equinox vehicles by providing a crafted MP3 file.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Mar 2023
- **Updated:** 19 Feb 2025
- **Also known as:** GHSA-cj8x-r7cp-9cjg

## What is CVE-2023-28885?

CVE-2023-28885 is a medium-severity memory corruption vulnerability in n/a, published on 27 Mar 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The 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.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2023-28885?

It affects 1 product.


Products: Gm Mylink Infotainment System.

## How do I fix CVE-2023-28885?

No fix has been published for CVE-2023-28885 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-28885 being exploited?

There is no known exploitation of CVE-2023-28885 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2023-39076](https://insights.sbomify.com/CVE-2023-39076/): Denial of service in n/a (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-28885 and fix it if it is affected.

What it is: CVE-2023-28885 is a medium-severity memory corruption vulnerability in n/a, published on 27 Mar 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-28885 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-28885/ (Markdown: https://insights.sbomify.com/CVE-2023-28885/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-28885
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-28885
- OSV: https://osv.dev/vulnerability/CVE-2023-28885

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-28885/
Summaries are generated and may contain mistakes; the official description above is the record.