# CVE-2023-6073: DoS and Control of Volume Settings for VW ID.3 ICAS3 IVI ECU

> Attackers can crash the vehicle's infotainment ECU and force maximum audio volume via REST API calls, affecting Volkswagen ID.3 and similar models.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Nov 2023
- **Updated:** 27 Feb 2025
- **Also known as:** GHSA-35gc-287r-3fpq

## What is CVE-2023-6073?

CVE-2023-6073 is a medium-severity denial of service vulnerability in Volkswagen ID.3, published on 10 Nov 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Attacker can perform a Denial of Service attack to crash the ICAS 3 IVI ECU in a Volkswagen ID.3 (and other vehicles of the VW Group with the same hardware) and spoof volume setting commands to irreversibly turn on audio volume to maximum via REST API calls.

Weakness: CWE-284 (Improper Access Control), CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Volkswagen Id.3 Firmware.

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

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

## Is CVE-2023-6073 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-6073 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2023-6073 is a medium-severity denial of service vulnerability in Volkswagen ID.3, published on 10 Nov 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-6073 exists.

Affected product: Volkswagen ID.3. 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-6073/ (Markdown: https://insights.sbomify.com/CVE-2023-6073/index.md)
```

## Sources

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

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