dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-24330

MEDIUM · 6.4 CVSS v3.1 Published 2025-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
66/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Sending a crafted SOAP "provision" operation message PlanId field within the Mobile Network Operator (MNO) internal Radio Access Network (RAN) management network can cause path traversal issue in Nokia Single RAN baseband software with versions earlier than release 24R1-SR 1.0 MP. This issue has been corrected to release 24R1-SR 1.0 MP and later. Beginning with release 24R1-SR 1.0 MP, the OAM service software performed PlanId field input validations mitigate the reported path traversal issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Path traversal vulnerability in Nokia Single RAN baseband software where a crafted SOAP 'provision' operation message with a malicious PlanId field can access files outside intended directories. The vulnerability exists in versions prior to 24R1-SR 1.0 MP within the MNO internal RAN management network.

MitigationUpgrade to release 24R1-SR 1.0 MP or later which implements PlanId field input validation to prevent path traversal attacks. Since this is internal network infrastructure, verify the upgrade does not impact existing RAN provisioning workflows.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
High
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine Nokia Single RAN software version
    Access the baseband software management interface or use the command line tool provided by Nokia (typically via OSS or netconf interface) to query the installed software version. Common commands include 'show software version' or checking the system information via the Nokia RAN management portal.
    Affected if The installed version is earlier than 24R1-SR 1.0 MP (e.g., 23R2, 24R0, etc.)
  2. Verify SOAP provision interface is accessible
    Check if the SOAP-based provisioning interface is enabled and reachable on the RAN management network. This is typically exposed on ports 8080, 8443, or custom ports configured for the Nokia RAN element manager. Review network access control lists and firewall rules surrounding the baseband units.
    Affected if The SOAP provision interface is exposed beyond the trusted MNO internal management network or is accessible without proper network segmentation.
  3. Identify PlanId field handling in provision operations
    Examine the SOAP provision operation messages processed by the baseband software. If you have access to logs or can capture/probe the interface, review how the PlanId parameter is validated. In affected versions, no input validation prevents path traversal sequences (../) in the PlanId field.
    Affected if The system processes PlanId fields without validating for path traversal characters, allowing access outside intended directories.
  4. Assess network exposure of RAN management interfaces
    Review the network topology and access controls for the internal RAN management network. Determine if the baseband management interfaces (where SOAP provision runs) are isolated from untrusted networks or if any external access paths exist.
    Affected if The management interface is accessible from network segments outside the trusted MNO internal RAN management network, increasing exploitation risk.

You are affected if your Nokia Single RAN baseband software version is earlier than 24R1-SR 1.0 MP and the SOAP provision interface is accessible within your environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to release 24R1-SR 1.0 MP or later which implements PlanId field input validation to prevent path traversal attacks. Since this is internal network infrastructure, verify the upgrade does not impact existing RAN provisioning workflows.

Recommended fix Moderate confidence

24R1-SR 1.0 MP

  1. Identify current Nokia Single RAN baseband software version in use
  2. Schedule a maintenance window for the upgrade
  3. Backup current system configuration before proceeding
  4. Upgrade Nokia Single RAN baseband software to release 24R1-SR 1.0 MP or later
  5. Verify the OAM service is running correctly after upgrade
  6. Confirm PlanId field input validations are active
Caveat No specific breaking changes mentioned in available documentation; verify compatibility with existing network configurations

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24330 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-24330 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data