dbcve.org
Dx Netops SpectrumApplication · Broadcom

CVE-2025-69272

HIGH · 7.5 CVSS v3.1 Published 2026-01-12
Fix available
A fix is available. Upgrade to 21.2.2 or later.
See remediation →
84/100
Remediation priority · High
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
Cleartext Transmission of Sensitive Information vulnerability in Broadcom DX NetOps Spectrum on Windows, Linux allows Sniffing Attacks.This issue affects DX NetOps Spectrum: 21.2.1 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

Broadcom DX NetOps Spectrum transmits sensitive information in cleartext (unencrypted) on Windows and Linux platforms, allowing remote attackers to intercept and read sensitive data via network sniffing. This is a network-level vulnerability that exposes communications between Spectrum components.

MitigationEnable TLS/SSL encryption for all DX NetOps Spectrum communications and ensure secure communication channels are configured for all network traffic between Spectrum components and clients.

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:< 21.2.2

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Determine installed Spectrum version
    Locate and inspect the DX NetOps Spectrum installation directory or use the Spectrum version reporting tool to identify the currently installed version number
    Affected if The installed version is lower than 21.2.2 (e.g., 21.2.1, 21.2.0, 20.x, etc.)
  2. Check TLS/SSL encryption status for Spectrum communications
    Review the Spectrum SSL/TLS configuration settings and verify whether encryption is enabled for communication between Spectrum components (SSDb, SpectroSERVER, OneClick)
    Affected if TLS/SSL encryption is disabled or not configured for Spectrum component communications
  3. Identify communication protocols in use
    Inspect the network configuration and protocol settings used by Spectrum to determine if unencrypted protocols (HTTP, non-TLS connections) are enabled for client and inter-component communication
    Affected if Cleartext protocols (HTTP, unencrypted ports) are actively used for Spectrum communications instead of encrypted alternatives
  4. Verify secure channel configuration for all traffic
    Review the Spectrum communication channel configuration to confirm that all network traffic between Spectrum components and clients is routed through encrypted channels
    Affected if Any Spectrum component-to-component or component-to-client traffic is configured to use unencrypted channels

A user is affected if their installed DX NetOps Spectrum version is below 21.2.2 AND cleartext (unencrypted) communications are enabled or configured for any Spectrum network traffic.

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

Enable TLS/SSL encryption for all DX NetOps Spectrum communications and ensure secure communication channels are configured for all network traffic between Spectrum components and clients.

Recommended fix Moderate confidence

21.2.2 or later

  1. Download DX NetOps Spectrum version 21.2.2 or later from the Broadcom Support Portal (support.broadcom.com)
  2. Review the DX NetOps Spectrum upgrade documentation for your platform (Windows or Linux)
  3. Ensure you have a complete backup of your current configuration and database
  4. Stop all Spectrum services before beginning the upgrade
  5. Run the upgrade installer for version 21.2.2 or later
  6. Verify all services start correctly after upgrade
  7. Confirm the vulnerability is resolved by checking that sensitive communications are now encrypted
Caveat Review upgrade documentation for any configuration changes required; test in non-production environment first

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

Fix this in Dx Netops Spectrum Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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