dbcve.org
Dx Netops SpectrumApplication · Broadcom

CVE-2025-69267

MEDIUM · 6.5 CVSS v3.1 Published 2026-01-12
Fix available
A fix is available. Upgrade to 24.3.9 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Improper Limitation of a Pathname to a Restricted Directory (Path Traversal) vulnerability in Broadcom DX NetOps Spectrum on Windows, Linux allows Path Traversal.This issue affects DX NetOps Spectrum: 24.3.8 and earlier.

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

A path traversal vulnerability exists in Broadcom DX NetOps Spectrum where the application fails to properly validate file path inputs, allowing attackers to use '..' directory traversal sequences to access files outside the intended restricted directories. This could enable unauthorized file access on both Windows and Linux deployments.

MitigationImplement strict input validation and path sanitization to ensure user-supplied path parameters cannot escape the intended directory bounds. Upgrade to a patched version when available, or apply vendor-supplied security updates.

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
Dx Netops SpectrumApplication
Affected:< 24.3.9

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

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

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 DX NetOps Spectrum version
    Locate the version information through the product UI (typically in About or System Information), or check installation configuration files and registry entries where version metadata is stored
    Affected if The installed version is any release prior to 24.3.9 (e.g., 24.3.0, 24.2.x, earlier releases)
  2. Determine if the web-based file handling interface is accessible
    Check if the Spectrum web application or REST API endpoints that accept file path parameters are exposed and operational
    Affected if The web interface or API is enabled and reachable, providing an attack surface for path traversal requests
  3. Review access logs for path traversal patterns
    Examine web server and application logs for requests containing '..' sequences or unusual directory references in file path parameters
    Affected if Log entries show '..' or directory traversal sequences in request parameters, indicating probing or exploitation attempts
  4. Inspect file system access outside intended directories
    Review the file system for any files or directories created or modified outside the designated Spectrum web root and restricted directories
    Affected if Files exist outside the expected web root or restricted directories, suggesting successful directory traversal access

A system is affected if it runs any version of Broadcom DX NetOps Spectrum prior to 24.3.9 and has the web interface or API accessible, since the vulnerability allows path traversal via '..' sequences to escape restricted directories.

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 24.3.9 or later
Fixed in 24.3.9
Interim mitigation

Implement strict input validation and path sanitization to ensure user-supplied path parameters cannot escape the intended directory bounds. Upgrade to a patched version when available, or apply vendor-supplied security updates.

Recommended fix Moderate confidence

24.3.9

  1. Upgrade DX NetOps Spectrum to version 24.3.9 or later to resolve the path traversal vulnerability
  2. Consult Broadcom support documentation (support.broadcom.com) for platform-specific upgrade instructions

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

Fix this in Dx Netops Spectrum Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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