dbcve.org
Hard-coded CredentialsWeakness · CWE-798

CVE-2025-4041

CRITICAL · 9.3 CVSS v4.0 Published 2025-05-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
In Optigo Networks ONS NC600 versions 4.2.1-084 through 4.7.2-330, an attacker could connect with the device's ssh server and utilize the system's components to perform OS command executions.

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

Authenticated command injection vulnerability in Optigo Networks ONS NC600 devices versions 4.2.1-084 through 4.7.2-330. An attacker with SSH access can execute arbitrary OS commands on the system by leveraging insecure handling of user input in system components.

MitigationUpgrade ONS NC600 firmware to vendor-provided patched version beyond 4.7.2-330. If immediate patching is not feasible, restrict SSH access to trusted management networks only via firewall or ACL rules.

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
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 device model is ONS NC600
    Access the device admin interface or check the device identification via CLI command such as 'show system info' or 'device info' to verify the exact model number
    Affected if The device is not an Optigo Networks ONS NC600 unit
  2. Check firmware version
    Use CLI command like 'show version' or 'firmware version' to retrieve the installed firmware version
    Affected if Firmware version falls within 4.2.1-084 through 4.7.2-330 (inclusive)
  3. Verify SSH service is enabled and accessible
    Check device network configuration for SSH service status using commands like 'show ssh status' or 'show service ssh', and determine if SSH port 22 is exposed to untrusted networks
    Affected if SSH is enabled and reachable from networks beyond trusted management interfaces
  4. Inspect for signs of command injection compromise
    Review system logs for unexpected commands or shell executions using 'show logs' or 'show audit log', and check for new unauthorized user accounts or modified system scripts
    Affected if Logs contain suspicious command executions, unexpected processes, or unauthorized configuration changes

You are affected if the device is an Optigo Networks ONS NC600 running firmware between versions 4.2.1-084 and 4.7.2-330 with SSH access available.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade ONS NC600 firmware to vendor-provided patched version beyond 4.7.2-330. If immediate patching is not feasible, restrict SSH access to trusted management networks only via firewall or ACL rules.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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