# CVE-2025-24334: The Nokia Single RAN baseband reveals its software version through the MNO internal RAN management network

> An attacker on the internal management network can reveal the exact software version of Nokia Single RAN basebands via a specific HTTP POST request.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jul 2025
- **Updated:** 2 Jul 2025
- **Also known as:** GHSA-f8r6-7g2p-2gpv

## What is CVE-2025-24334?

CVE-2025-24334 is a low-severity vulnerability in Nokia Single RAN, published on 2 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Nokia Single RAN baseband software earlier than 23R2-SR 1.0 MP can be made to reveal the exact software release version by sending a specific HTTP POST request through the Mobile Network Operator (MNO) internal RAN management network.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere)

## Which versions are affected by CVE-2025-24334?


## How do I fix CVE-2025-24334?

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

## Is CVE-2025-24334 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-24334 and fix it if it is affected.

What it is: CVE-2025-24334 is a low-severity vulnerability in Nokia Single RAN, published on 2 Jul 2025. 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-2025-24334 in the wild and no public exploit code.

Affected product: Nokia Single RAN. 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-2025-24334/ (Markdown: https://insights.sbomify.com/CVE-2025-24334/index.md)
```

## Sources

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

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