# CVE-2023-52238: Information disclosure in RUGGEDCOM RST2228

> A low-privileged user can retrieve the MACSEC key from the web server, allowing decryption of ethernet frames.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/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:** 9 Jul 2024
- **Updated:** 27 Aug 2025
- **Also known as:** GHSA-jfvv-8342-x746

## What is CVE-2023-52238?

CVE-2023-52238 is a low-severity vulnerability in Siemens RUGGEDCOM RST2228, published on 9 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability has been identified in RUGGEDCOM RST2228 (All versions < V5.9.0), RUGGEDCOM RST2228P (All versions < V5.9.0). The web server of the affected systems leaks the MACSEC key in clear text to a logged in user. An attacker with the credentials of a low privileged user could retrieve the MACSEC key and access (decrypt) the ethernet frames sent by authorized recipients.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2023-52238 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-52238 is a low-severity vulnerability in Siemens RUGGEDCOM RST2228, published on 9 Jul 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-52238 in the wild and no public exploit code.

Affected product: Siemens RUGGEDCOM RST2228. 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-52238/ (Markdown: https://insights.sbomify.com/CVE-2023-52238/index.md)
```

## Sources

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

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