dbcve.org
Mantaray NmApplication · Nokia

CVE-2025-24817

HIGH · 8.0 CVSS v3.1 Published 2026-04-07
Fix available
A fix is available. Upgrade to 25r1-nm or later.
See remediation →
82/100
Remediation priority · High
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 MantaRay NM is vulnerable to an OS command injection vulnerability due to improper neutralization of special elements used in an OS command in Symptom Collector application.

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

Nokia MantaRay NM's Symptom Collector application is vulnerable to OS command injection due to improper neutralization of special elements in OS commands. This allows an attacker to execute arbitrary operating system commands on the affected device by injecting malicious command sequences through user-supplied input that gets passed to system call functions.

MitigationImplement strict input validation and use parameterized APIs or safe library functions instead of constructing OS commands from user input. If OS command execution is unavoidable, employ allowlist-based validation and avoid passing unsanitized user input to shell interpreters.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mantaray NmApplication
Affected:< 25r1-nm

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

CVSS:3.1/AV:A/AC:L/PR:L/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 MantaRay NM version
    Locate the NM installation directory and check the version manifest or version file. Common locations include /opt/nm, /usr/local/nm, or the installation root directory. Look for version information in files named version, ver.info, or similar.
    Affected if The installed version is any release prior to 25r1-nm (for example, 24r2, 24r1, or earlier releases).
  2. Confirm the Symptom Collector application is present
    Check if the Symptom Collector module or application is installed on the NM system. Look for directories or binaries related to 'symptom', 'collector', or 'nm-collector' within the NM installation path.
    Affected if The Symptom Collector application exists on the system, indicating the vulnerable component is present.
  3. Determine if Symptom Collector is enabled or configured
    Review the NM configuration files for settings that enable or activate the Symptom Collector feature. Check configuration files in /config, /etc/nm, or the NM home directory for entries like 'symptom_collector_enabled', 'collector_mode', or similar toggles.
    Affected if The Symptom Collector feature is enabled or actively configured in the NM setup.
  4. Inspect user input pathways to Symptom Collector
    Examine NM configuration or log files that show how user-supplied data reaches the Symptom Collector. Look for parameters, input fields, or API endpoints that feed data to the collector functionality.
    Affected if User-supplied input can be passed directly to the Symptom Collector without sanitization, which would enable command injection.

A system is affected if it runs any version of Nokia MantaRay NM prior to 25r1-nm and has the Symptom Collector application enabled with user input pathways that can reach OS command execution functions.

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
Upgrade available Upgrade to 25r1-nm or later
Fixed in 25r1-nm
Interim mitigation

Implement strict input validation and use parameterized APIs or safe library functions instead of constructing OS commands from user input. If OS command execution is unavoidable, employ allowlist-based validation and avoid passing unsanitized user input to shell interpreters.

Recommended fix Moderate confidence

25r1-nm

  1. Obtain the Nokia MantaRay NM version 25r1-nm or later from Nokia's official distribution channels
  2. Review Nokia's official upgrade documentation for MantaRay NM before proceeding
  3. Back up current MantaRay NM configuration and data according to Nokia backup procedures
  4. Apply the upgrade to MantaRay NM following Nokia's standard upgrade process
  5. After upgrade, verify the Symptom Collector application is functioning correctly
  6. Confirm the vulnerability is resolved by checking that command injection is no longer possible in the Symptom Collector

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

Fix this in Mantaray Nm Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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