dbcve.org
Command InjectionWeakness · CWE-77

CVE-2025-24333

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
Nokia Single RAN baseband software earlier than 24R1-SR 1.0 MP contains administrative shell input validation fault, which authenticated admin user can, in theory, potentially use for injecting arbitrary commands for unprivileged baseband OAM service process execution via special characters added to baseband internal COMA_config.xml file. This issue has been corrected starting from release 24R1-SR 1.0 MP and later, by adding proper input validation to OAM service process which prevents injecting special characters via baseband internal COMA_config.xml file.

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

Nokia Single RAN baseband software prior to version 24R1-SR 1.0 MP contains an input validation vulnerability in the OAM service process. An authenticated administrator can inject arbitrary commands into the baseband OAM service by adding special characters to the COMA_config.xml configuration file, achieving unprivileged command execution.

MitigationUpgrade Nokia Single RAN baseband software to version 24R1-SR 1.0 MP or later, which implements proper input validation in the OAM service process to prevent command injection via the COMA_config.xml file.

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
Local
Complexity
High
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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. Confirm Nokia Single RAN baseband software is installed
    Identify the installed baseband software product on the system
    Affected if The system is running Nokia Single RAN baseband software and the version is prior to 24R1-SR 1.0 MP
  2. Check the software version
    Retrieve the installed version of the Nokia Single RAN baseband software and compare it against the affected range
    Affected if The installed version is earlier than 24R1-SR 1.0 MP (the fixed version)
  3. Verify the OAM service process is present
    Identify if the OAM (Operations, Administration, and Management) service process is running on the system
    Affected if The OAM service process is present and the software version is prior to 24R1-SR 1.0 MP
  4. Locate the COMA_config.xml configuration file
    Search for the COMA_config.xml file in the OAM service configuration directory
    Affected if The COMA_config.xml file exists and contains special characters that could indicate command injection attempts, combined with software version prior to 24R1-SR 1.0 MP

A system is affected if it runs Nokia Single RAN baseband software versions prior to 24R1-SR 1.0 MP with the OAM service enabled and the COMA_config.xml configuration file present.

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 version 24R1-SR 1.0 MP or later, which implements proper input validation in the OAM service process to prevent command injection via the COMA_config.xml file.

Recommended fix High confidence

24R1-SR 1.0 MP or later

  1. Identify the current version of Nokia Single RAN baseband software by accessing the OAM service admin interface
  2. Plan and schedule an upgrade window following Nokia's standard maintenance procedures
  3. Upgrade the Nokia Single RAN baseband software to release 24R1-SR 1.0 MP or later
  4. After upgrade, verify that the OAM service process is running correctly and that the COMA_config.xml file is now properly validated
  5. Confirm the fix by checking that special characters in the COMA_config.xml file can no longer be used to inject arbitrary commands

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing16.0 h
  • Review / QA8.0 h
36.0 hours of engineering $6,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24333 — 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-24333 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