dbcve.org
Dx Netops SpectrumApplication · Broadcom

CVE-2025-69274

HIGH · 8.8 CVSS v3.1 Published 2026-01-12
Fix available
A fix is available. Upgrade to 24.3.11 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Authorization Bypass Through User-Controlled Key vulnerability in Broadcom DX NetOps Spectrum on Windows, Linux allows Privilege Escalation.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

An authorization bypass vulnerability in Broadcom DX NetOps Spectrum allows authenticated users to manipulate user-controlled keys (such as parameters or identifiers) to bypass authorization checks, enabling privilege escalation from standard user to administrative or higher privilege levels.

MitigationUpgrade to DX NetOps Spectrum version 24.3.11 or later which contains the fix. Apply network segmentation and monitor for anomalous authorization requests as interim controls if patching is delayed.

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

CVSS:3.1/AV:N/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 if Broadcom DX NetOps Spectrum is installed
    Locate the Spectrum installation directory or check for Spectrum processes/services running on the system. Common locations include /opt/CA/Spectrum or C:\CA\Spectrum on Windows.
    Affected if DX NetOps Spectrum software is present on the system
  2. Determine the installed version of DX NetOps Spectrum
    Check the installed version using the Spectrum administrative interface, command-line tools, or version files within the installation directory. Look for a version file or use the Spectrum diagnostic commands.
    Affected if The installed version number is lower than 24.3.11 (e.g., 24.2.x, 24.1.x, earlier releases)
  3. Verify if the web-based administration interface or REST API is accessible
    Confirm that the Spectrum OneClick web console or REST API endpoints are exposed and reachable. Check if port 8080 or 8443 (or configured HTTPS ports) are listening.
    Affected if The web interface or API is accessible from network locations where standard users can authenticate
  4. Confirm user authentication is enabled and standard users exist
    Review Spectrum user management settings to verify standard (non-admin) user accounts are configured and can log in to the OneClick console or API.
    Affected if Standard user accounts exist and can authenticate, providing the context for the authorization bypass to be exploited

If DX NetOps Spectrum is installed with a version lower than 24.3.11 and standard users can authenticate to the web interface or API, the environment is potentially affected by this authorization bypass vulnerability.

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 which contains the fix. Apply network segmentation and monitor for anomalous authorization requests as interim controls if patching is delayed.

Recommended fix High confidence

Upgrade to DX NetOps Spectrum 24.3.11

  1. Verify current DX NetOps Spectrum version using the Spectrum Administration UI or command-line tools
  2. Review the upgrade documentation for DX NetOps Spectrum 24.3.11 on support.broadcom.com
  3. Plan maintenance window as upgrade may require system downtime
  4. Create a complete backup of the Spectrum database and configuration
  5. Download DX NetOps Spectrum 24.3.11 from Broadcom Support Portal
  6. Execute the upgrade following the official 24.3.11 upgrade instructions
  7. Verify the upgrade completed successfully and Spectrum services are running
  8. Validate that the IDOR vulnerability is remediated by confirming proper authorization controls
Caveat Review 24.3.11 release notes for any configuration or behavioral changes 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
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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