# CVE-2023-32228: Auth bypass in AMS

> A firmware bug in Bosch access control devices allows an adversary to bypass authentication and gain access as the last authorized user.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:P/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:** 11 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-vc49-qc4g-2225

## What is CVE-2023-32228?

CVE-2023-32228 is a medium-severity authentication bypass vulnerability in Bosch AMS, published on 11 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A firmware bug which may lead to misinterpretation of data in the AMC2-4WCF and AMC2-2WCF allowing an adversary to grant access to the last authorized user.

Weakness: CWE-115 (Misinterpretation of Input)

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


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

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

## Is CVE-2023-32228 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-32228 is a medium-severity authentication bypass vulnerability in Bosch AMS, published on 11 Apr 2024. 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-32228 in the wild and no public exploit code.

Affected product: Bosch AMS. 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-32228/ (Markdown: https://insights.sbomify.com/CVE-2023-32228/index.md)
```

## Sources

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

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