# CVE-2022-40633: Rittal CMC III Improper Access Control

> Attackers can clone access cards to bypass physical security controls on Rittal CMC III cabinets, requiring vendor mitigation.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 2 Mar 2023
- **Updated:** 17 Jan 2025
- **Also known as:** GHSA-q4g5-vhgq-vfr3

## What is CVE-2022-40633?

CVE-2022-40633 is a medium-severity vulnerability in Rittal CMC III, published on 2 Mar 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A malicious actor can clone access cards used to open control cabinets secured with Rittal CMC III locks.

## Which versions are affected by CVE-2022-40633?

It affects 1 product.


Products: Rittal Cmc Iii Firmware.

## How do I fix CVE-2022-40633?

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

## Is CVE-2022-40633 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-40633 and fix it if it is affected.

What it is: CVE-2022-40633 is a medium-severity vulnerability in Rittal CMC III, published on 2 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-2022-40633 in the wild and no public exploit code.

Affected product: Rittal CMC III. 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-2022-40633/ (Markdown: https://insights.sbomify.com/CVE-2022-40633/index.md)
```

## Sources

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

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