# CVE-2018-9322: Security feature bypass in n/a

> Local attackers can bypass firmware code-signing via USB or OBD-II to gain root access on BMW infotainment systems.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 31 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** CVE-2018-9323, GHSA-5937-mjcm-vj8m

## What is CVE-2018-9322?

CVE-2018-9322 is a high-severity vulnerability in n/a, published on 31 May 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Head Unit HU_NBT (aka Infotainment) component on BMW i Series, BMW X Series, BMW 3 Series, BMW 5 Series, and BMW 7 Series vehicles produced in 2012 through 2018 allows local attacks involving the USB or OBD-II interface. An attacker can bypass the code-signing protection mechanism for firmware updates, and consequently obtain a root shell.

Weakness: CWE-693 (Protection Mechanism Failure)

## Which versions are affected by CVE-2018-9322?

It affects 1 product.


Products: Bmw Head Unit Hu Nbt Firmware.

## How do I fix CVE-2018-9322?

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

## Is CVE-2018-9322 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-9312](https://insights.sbomify.com/CVE-2018-9312/): Security feature bypass in n/a (high 7.8)
- [CVE-2018-9320](https://insights.sbomify.com/CVE-2018-9320/): Security feature bypass in n/a (high 7.8)
- [CVE-2018-9314](https://insights.sbomify.com/CVE-2018-9314/): Security feature bypass in n/a (medium 6.8)
- [CVE-2018-9313](https://insights.sbomify.com/CVE-2018-9313/): Denial of service in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-9322 and fix it if it is affected.

What it is: CVE-2018-9322 is a high-severity vulnerability in n/a, published on 31 May 2018. 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-2018-9322 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-2018-9322/ (Markdown: https://insights.sbomify.com/CVE-2018-9322/index.md)
```

## Sources

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

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