# CVE-2023-32219: Mazda cars unlocking

> Attackers can bypass authentication to unlock specific Mazda vehicles, posing a physical security risk to owners.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **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:** 12 Jun 2023
- **Updated:** 6 Jan 2025
- **Also known as:** GHSA-hr5f-9r38-h32r

## What is CVE-2023-32219?

CVE-2023-32219 is a medium-severity authentication bypass vulnerability in Mazda (2015-2016), published on 12 Jun 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A Mazda model (2015-2016) can be unlocked via an unspecified method.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Mazda Mazda Firmware.

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

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

## Is CVE-2023-32219 being exploited?

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

## Other vulnerabilities in Mazda (2015-2016)

- [CVE-2022-36945](https://insights.sbomify.com/CVE-2022-36945/): Security feature bypass in n/a (medium 6.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-32219 is a medium-severity authentication bypass vulnerability in Mazda (2015-2016), published on 12 Jun 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-32219 in the wild and no public exploit code.

Affected product: Mazda (2015-2016). 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-32219/ (Markdown: https://insights.sbomify.com/CVE-2023-32219/index.md)
```

## Sources

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

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