# CVE-2024-47945: Predictable Session ID

> Attackers can hijack user sessions by predicting low-entropy session IDs generated with insecure random functions, leading to unauthorized access.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Oct 2024
- **Updated:** 3 Nov 2025
- **Also known as:** GHSA-3qfw-5g24-8pmq

## What is CVE-2024-47945?

CVE-2024-47945 is a critical authentication bypass vulnerability in RITTAL GmbH & Co. KG IoT Interface & CMC III Processing Unit, published on 15 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The devices are vulnerable to session hijacking due to insufficient 
entropy in its session ID generation algorithm. The session IDs are 
predictable, with only 32,768 possible values per user, which allows 
attackers to pre-generate valid session IDs, leading to unauthorized 
access to user sessions. This is not only due to the use of an 
(insecure) rand() function call but also because of missing 
initialization via srand(). As a result only the PIDs are effectively 
used as seed.

Weakness: CWE-331 (Insufficient Entropy), CWE-340 (Generation of Predictable Numbers or Identifiers)

## Which versions are affected by CVE-2024-47945?

It affects 2 products.


Products: Rittal Cmc Iii Processing Units Firmware, Rittal Iot Interface Firmware.

## How do I fix CVE-2024-47945?

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

## Is CVE-2024-47945 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-47945 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-47945 and fix it if it is affected.

What it is: CVE-2024-47945 is a critical authentication bypass vulnerability in RITTAL GmbH & Co. KG IoT Interface & CMC III Processing Unit, published on 15 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-47945 exists.

Affected product: RITTAL GmbH & Co. KG IoT Interface & CMC III Processing Unit. 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-2024-47945/ (Markdown: https://insights.sbomify.com/CVE-2024-47945/index.md)
```

## Sources

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

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