dbcve.org
Dx Netops SpectrumApplication · Broadcom

CVE-2025-69273

HIGH · 7.5 CVSS v3.1 Published 2026-01-12
Fix available
A fix is available. Upgrade to 24.3.11 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
Improper Authentication vulnerability in Broadcom DX NetOps Spectrum on Windows, Linux allows Authentication Bypass.This issue affects DX NetOps Spectrum: 24.3.10 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

Improper Authentication vulnerability in Broadcom DX NetOps Spectrum versions 24.3.10 and earlier on Windows and Linux allows authentication bypass, enabling unauthenticated attackers to potentially gain unauthorized access to the network operations management platform.

MitigationUpgrade to DX NetOps Spectrum version 24.3.11 or later once the patch is released. Implement network segmentation and access controls to limit exposure to the Spectrum management interfaces as an interim measure.

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.11

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. Identify DX NetOps Spectrum installation directory
    Locate the Spectrum installation path. On Linux, typically under /opt/CA/Spectrum or /opt/Broadcom/Spectrum. On Windows, commonly under C:\Program Files\CA\Spectrum or C:\Program Files\Broadcom\Spectrum. Check for the Spectrum directory structure containing bin, lib, or tomcat folders.
    Affected if The Spectrum software is installed in the environment on Windows or Linux.
  2. Determine installed Spectrum version
    Look for a version file or executable. Common locations: <install_dir>/install_dir_version file, <install_dir>/.version, or execute <install_dir>/bin/SpectrumConfig.sh (Linux) or SpectrumConfig.bat (Windows) if available. Alternatively, check theSpectroSERVER process version or look in the <install_dir>/README or <install_dir>/version.txt file.
    Affected if The version number returned is 24.3.10 or earlier, or the version cannot be determined but the software appears to be installed.
  3. Verify platform is Windows or Linux
    Confirm the operating system where Spectrum is installed by running 'uname' on Linux or checking System Properties on Windows. The vulnerability specifically affects Windows and Linux platforms.
    Affected if The Spectrum installation is running on Windows or Linux operating systems.
  4. Check if Spectrum management interfaces are exposed
    Review network configuration for Spectrum-related ports. Default Spectrum ports include 8080, 8443 (HTTP/HTTPS), and 162/162 (SNMP). Check firewall rules and network access control lists to determine if these management interfaces are accessible from untrusted networks.
    Affected if The Spectrum management web interface or SNMP services are exposed to networks outside the trusted internal network.

The environment is affected if Broadcom DX NetOps Spectrum version 24.3.10 or earlier is installed on Windows or Linux and the management interfaces are network-accessible.

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.11 or later
Fixed in 24.3.11
Interim mitigation

Upgrade to DX NetOps Spectrum version 24.3.11 or later once the patch is released. Implement network segmentation and access controls to limit exposure to the Spectrum management interfaces as an interim measure.

Recommended fix High confidence

24.3.11 or later

  1. 1. Identify the current DX NetOps Spectrum version by checking the installed software or using the Spectrum Administration UI
  2. 2. Navigate to the Broadcom Support Portal at support.broadcom.com
  3. 3. Locate and download DX NetOps Spectrum version 24.3.11 or later
  4. 4. Review the upgrade documentation and release notes for version 24.3.11
  5. 5. Back up the current DX NetOps Spectrum installation and database
  6. 6. Stop the DX NetOps Spectrum services
  7. 7. Install or upgrade to version 24.3.11 following the standard Broadcom upgrade procedures
  8. 8. Verify the installation and ensure all services start correctly
Caveat Review release notes for any configuration or behavioral changes between your current version and 24.3.11 before upgrading

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
  • 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-69273 — 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-69273 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