Skip to main content

CVE-2023-5649: Brocade ASCG Input Validation DoS Vulnerability

CVE-2023-5649 is an input validation flaw in Broadcom Brocade Active Support Connectivity Gateway that enables authenticated users to trigger denial of service. This post covers technical details, affected versions, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2023-5649 Overview

CVE-2023-5649 is an improper input validation vulnerability [CWE-20] in Broadcom Brocade Active Support Connectivity Gateway (ASCG) versions before 3.0. The flaw affects the registered case credentials handling when the gateway collects a supportsave from a Brocade Switch. A local authenticated user can supply special characters as input, triggering a Denial of Service (DoS) condition in the support data collection workflow.

Critical Impact

An authenticated local user can disrupt supportsave collection from Brocade Switches, interrupting diagnostic and support operations on the ASCG appliance.

Affected Products

  • Broadcom Brocade Active Support Connectivity Gateway (ASCG) versions prior to 3.0

Discovery Timeline

  • 2026-10-08 - CVE-2023-5649 published to NVD
  • 2026-10-14 - Last updated in NVD database

Technical Details for CVE-2023-5649

Vulnerability Analysis

The vulnerability resides in the credential input handling path used when the Brocade ASCG initiates a supportsave collection from a connected Brocade Switch. The registered case credentials field does not sanitize or reject invalid input such as shell metacharacters and other special characters. When unsanitized input reaches the downstream collection routine, the operation fails in a manner that produces a Denial of Service.

The impact is limited to availability. The CVSS vector indicates no confidentiality or integrity impact and no scope change. Exploitation requires local access with low privileges and no user interaction, so a legitimate authenticated operator could inadvertently or deliberately disrupt support data collection.

Root Cause

The root cause is missing input validation on the registered case credentials field [CWE-20]. The application accepts arbitrary character sequences, including special characters, without validating them against the expected credential format before passing the value to the supportsave collection logic.

Attack Vector

An attacker must authenticate locally to the ASCG with at least low-privilege access. The attacker then submits a crafted credential string containing special characters through the registered case credentials interface. When ASCG attempts to use those credentials to collect supportsave output from a Brocade Switch, the operation fails and the availability of the support collection function is disrupted.

No exploit code is publicly available, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog. See the Broadcom Security Advisory #22716 for vendor-supplied details.

Detection Methods for CVE-2023-5649

Indicators of Compromise

  • Repeated failures of supportsave collection jobs on ASCG against one or more Brocade Switches.
  • Error entries in ASCG application logs referencing invalid credential input or aborted support collection tasks.
  • Credential records containing shell metacharacters or other non-standard characters in the registered case configuration.

Detection Strategies

  • Review ASCG audit logs for authenticated users modifying registered case credentials followed by failed supportsave operations.
  • Correlate credential update events with subsequent service availability errors in the support collection subsystem.
  • Monitor for anomalous local authenticated sessions interacting with the credential management interface.

Monitoring Recommendations

  • Forward ASCG application and audit logs to a centralized SIEM for retention and correlation.
  • Alert on repeated supportsave failures tied to the same user or credential record within a short time window.
  • Track administrative changes to registered case credentials and require review of changes made by non-administrative accounts.

How to Mitigate CVE-2023-5649

Immediate Actions Required

  • Upgrade Brocade ASCG to version 3.0 or later as directed by the Broadcom advisory.
  • Restrict local authenticated access to the ASCG to trusted operators only.
  • Audit existing registered case credential entries and remove any containing unexpected special characters.

Patch Information

Broadcom addressed the issue in Brocade ASCG version 3.0. Refer to Broadcom Security Advisory #22716 for the official fixed version and upgrade guidance.

Workarounds

  • Limit which accounts can modify registered case credentials on the ASCG.
  • Enforce a credential format policy that excludes shell metacharacters and other special characters prior to entry.
  • Validate that supportsave collection succeeds after any credential change, and roll back credentials that cause failures.
bash
# Verify ASCG version and plan upgrade to 3.0 or later
# (consult the Broadcom advisory for exact upgrade procedure)
ascg --version

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.