# CVE-2022-46140: Weak cryptography in RUGGEDCOM RM1224 LTE(4G) EU

> An authenticated attacker can decrypt debug zip files to retrieve sensitive system information due to weak encryption.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Dec 2022
- **Updated:** 21 Apr 2025
- **Also known as:** GHSA-39hc-9gp8-p9wh

## What is CVE-2022-46140?

CVE-2022-46140 is a high-severity vulnerability in Siemens RUGGEDCOM RM1224 LTE(4G) EU, published on 13 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Affected devices use a weak encryption scheme to encrypt the debug zip file. This could allow an authenticated attacker to decrypt the contents of the file and retrieve debug information about the system.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

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

It affects 101 products.


Products: Siemens Ruggedcom Rm1224 Lte\(4g\) Eu Firmware, Siemens Ruggedcom Rm1224 Lte\(4g\) Nam Firmware, Siemens Scalance M804pb Firmware, Siemens Scalance M812-1 Adsl-Router Firmware, Siemens Scalance M816-1 Adsl-Router Firmware, Siemens Scalance M826-2 Shdsl-Router Firmware, Siemens Scalance M874-2 Firmware, Siemens Scalance M874-3 Firmware, Siemens Scalance M876-3 Firmware, Siemens Scalance M876-4 Firmware, Siemens Scalance Mum853-1 Firmware, Siemens Scalance Mum856-1 Firmware, Siemens Scalance S615 Eec Firmware, Siemens Scalance S615 Firmware, Siemens Scalance Sc622-2c Firmware, Siemens Scalance Sc626-2c Firmware, Siemens Scalance Sc632-2c Firmware, Siemens Scalance Sc636-2c Firmware, Siemens Scalance Sc642-2c Firmware, Siemens Scalance Sc646-2c Firmware and 81 more.

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

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

## Is CVE-2022-46140 being exploited?

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

## Other vulnerabilities in Siemens RUGGEDCOM RM1224 LTE(4G) EU

- [CVE-2024-50557](https://insights.sbomify.com/CVE-2024-50557/): Command injection in RUGGEDCOM RM1224 LTE(4G) EU (high 8.6)
- [CVE-2024-50572](https://insights.sbomify.com/CVE-2024-50572/): Command injection in RUGGEDCOM RM1224 LTE(4G) EU (high 8.6)
- [CVE-2024-41976](https://insights.sbomify.com/CVE-2024-41976/): Code injection in RUGGEDCOM RM1224 LTE(4G) EU (high 8.6)
- [CVE-2024-41977](https://insights.sbomify.com/CVE-2024-41977/): Privilege escalation in RUGGEDCOM RM1224 LTE(4G) EU (high 7.3)
- [CVE-2024-41978](https://insights.sbomify.com/CVE-2024-41978/): Information disclosure in RUGGEDCOM RM1224 LTE(4G) EU (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-46140 is a high-severity vulnerability in Siemens RUGGEDCOM RM1224 LTE(4G) EU, published on 13 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-46140 in the wild and no public exploit code.

Affected product: Siemens RUGGEDCOM RM1224 LTE(4G) EU. 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-46140/ (Markdown: https://insights.sbomify.com/CVE-2022-46140/index.md)
```

## Sources

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

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