# CVE-2023-44318: Hardcoded credentials in RUGGEDCOM RM1224 LTE(4G) EU

> An attacker with admin access or a backup file can use a hardcoded key to decrypt and read sensitive configuration data from Siemens industrial routers.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Nov 2023
- **Updated:** 25 Feb 2026
- **Also known as:** GHSA-xhv6-jc84-h9c6

## What is CVE-2023-44318?

CVE-2023-44318 is a medium-severity vulnerability in Siemens RUGGEDCOM RM1224 LTE(4G) EU, published on 14 Nov 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Affected devices use a hardcoded key to obfuscate the configuration backup that an administrator can export from the device. This could allow an authenticated attacker with administrative privileges or an attacker that obtains a configuration backup to extract configuration information from the exported file.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

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

It affects 71 products.


Products: Siemens 6ag1206-2bb00-7ac2 Firmware, Siemens 6ag1206-2bs00-7ac2 Firmware, Siemens 6ag1208-0ba00-7ac2 Firmware, Siemens 6ag1216-4bs00-7ac2 Firmware, Siemens 6gk5204-0ba00-2gf2 Firmware, Siemens 6gk5204-0ba00-2yf2 Firmware, Siemens 6gk5204-2aa00-2gf2 Firmware, Siemens 6gk5204-2aa00-2yf2 Firmware, Siemens 6gk5205-3bb00-2ab2 Firmware, Siemens 6gk5205-3bb00-2tb2 Firmware, Siemens 6gk5205-3bd00-2ab2 Firmware, Siemens 6gk5205-3bd00-2tb2 Firmware, Siemens 6gk5205-3bf00-2ab2 Firmware, Siemens 6gk5205-3bf00-2tb2 Firmware, Siemens 6gk5206-2bb00-2ac2 Firmware, Siemens 6gk5206-2bd00-2ac2 Firmware, Siemens 6gk5206-2bs00-2ac2 Firmware, Siemens 6gk5206-2bs00-2fc2 Firmware, Siemens 6gk5206-2gs00-2ac2 Firmware, Siemens 6gk5206-2gs00-2fc2 Firmware and 51 more.

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

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

## Is CVE-2023-44318 being exploited?

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

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

- [CVE-2023-44373](https://insights.sbomify.com/CVE-2023-44373/): Command injection in RUGGEDCOM RM1224 LTE(4G) EU (critical 9.4)
- [CVE-2022-31765](https://insights.sbomify.com/CVE-2022-31765/): Missing authorization in RUGGEDCOM RM1224 LTE(4G) EU (high 8.8)
- [CVE-2023-44374](https://insights.sbomify.com/CVE-2023-44374/): Race condition in RUGGEDCOM RM1224 LTE(4G) EU (high 7.1)
- [CVE-2023-44319](https://insights.sbomify.com/CVE-2023-44319/): Weak cryptography in RUGGEDCOM RM1224 LTE(4G) EU (medium 6.9)
- [CVE-2023-44321](https://insights.sbomify.com/CVE-2023-44321/): Denial of service in RUGGEDCOM RM1224 LTE(4G) EU (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-44318 is a medium-severity vulnerability in Siemens RUGGEDCOM RM1224 LTE(4G) EU, published on 14 Nov 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-44318 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-2023-44318/ (Markdown: https://insights.sbomify.com/CVE-2023-44318/index.md)
```

## Sources

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

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