dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-24329

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 archive 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 utilizes libarchive APIs with security options enabled, effectively mitigating 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 · high confidence

A path traversal vulnerability exists in Nokia Single RAN baseband software versions earlier than 24R1-SR 1.0 MP. The issue is triggered by a crafted SOAP provision operation message containing a malicious archive field, allowing unauthorized file writes outside intended directories. The fix in release 24R1-SR 1.0 MP enables security options in libarchive APIs to block path traversal attacks.

MitigationUpgrade Nokia Single RAN baseband software to release 24R1-SR 1.0 MP or later, which implements libarchive APIs with security options enabled.

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. Identify the installed Nokia Single RAN baseband software version
    Use the system's version reporting command or check the software release information (typically accessible via admin interface or system info command). Compare the version string to '24R1-SR 1.0 MP'.
    Affected if The installed version is earlier than 24R1-SR 1.0 MP (e.g., 24R1-SR 0.x, 23.x, or any version number that precedes 24R1-SR 1.0 MP).
  2. Determine if SOAP provision operations are enabled
    Check the configuration settings for the Nokia Single RAN baseband software's provision interface. Look for SOAP-based provision operation settings or XML/SOAP service configurations.
    Affected if SOAP provision operations are enabled and accessible (the vulnerability is triggered specifically by crafted SOAP provision operation messages).
  3. Verify the libarchive security configuration
    Examine the libarchive library configuration or settings used by the provision operation handler. Look for security-related flags or options in the archive processing configuration.
    Affected if The libarchive APIs do not have security options enabled, or path traversal protection is not explicitly configured (the vulnerability exists when these protections are missing).
  4. Check for recent SOAP provision operation logs
    Review system logs or audit logs for SOAP provision operation requests, particularly those involving archive field processing. Look for any anomalous archive extraction patterns.
    Affected if There are SOAP provision operation logs showing archive field processing without proper path validation, or unexpected file write locations outside intended directories.

You are affected if your Nokia Single RAN baseband software version is earlier than 24R1-SR 1.0 MP and SOAP provision operations with archive fields are enabled without libarchive security protections in place.

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 Nokia Single RAN baseband software to release 24R1-SR 1.0 MP or later, which implements libarchive APIs with security options enabled.

Recommended fix High confidence

24R1-SR 1.0 MP

  1. 1. Identify the current version of Nokia Single RAN baseband software running in the MNO RAN management network.
  2. 2. If the version is earlier than 24R1-SR 1.0 MP, plan for an upgrade to release 24R1-SR 1.0 MP or later.
  3. 3. Obtain the upgrade package from Nokia through official channels.
  4. 4. Schedule a maintenance window following Nokia's recommended upgrade procedure for Single RAN baseband software.
  5. 5. Apply the upgrade to all affected Single RAN baseband units.
  6. 6. Verify the upgrade was successful by checking the software version and confirming the OAM service is running correctly.
Caveat Standard telecom upgrade procedures apply; ensure compatibility testing with existing network configuration before production deployment

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-24329 — 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-24329 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