Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain foothold on adjacent network
-
ExploitReach ASCG admin API service
-
ExecutionSend unauthenticated privileged API request
-
ImpactRead config and alter device inventory/settings
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication required for critical functions
MITRE ATT&CK
1 technique across 1 tactic: Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires network reachability to the Brocade ASCG administrative management service from an adjacent network position (CVSS AV:A), not arbitrary internet-based access - the attacker must be able to route to the appliance's management/API interface on the local or logically adjacent segment. Once reachable, no authentication (PR:N) and no user interaction (UI:N) are needed, and this holds against default configurations because the missing-authentication flaw is in the privileged API itself; any ASCG instance before version 3.5.0 is affected. The primary limiting factor is the adjacent-network precondition - an internet-exposed, segmented, or firewalled management interface significantly reduces exploitability. |
| Impact | This is a genuine high-priority issue, though its reach is bounded by the attack vector. The CVSS 4.0 base score of 8.7 (High) is driven by CWE-306 (Missing Authentication for a Critical Function): an attacker needs no privileges (PR:N), no user interaction (UI:N), and faces low attack complexity (AC:L) and no special attack requirements (AT:N), while achieving high confidentiality and integrity impact (VC:H/VI:H) with low availability impact (VA:L). The single most important mitigating signal is AV:A (Adjacent), not Network - exploitation requires the attacker to be on the same adjacent/logical network as the ASCG management service rather than reaching it from the open internet, which materially narrows realistic exposure. Several dynamic risk signals are absent from the input: no EPSS probability, no CISA KEV listing, and no indication of public POC code, so exploitation status is 'no public exploit identified at time of analysis.' No SSVC decision data was provided. There is no conflict between the CVSS vector and the description - both agree on unauthenticated access to privileged administrative API functions - but the confidentiality/integrity-high, availability-low profile aligns with data exposure and configuration tampering rather than service disruption. Net: treat as a prompt-patch item for any environment running ASCG, with urgency tempered by the adjacent-network precondition and the current absence of known exploitation. |
| Exploit ScenarioDerived | An attacker who has gained a foothold on the adjacent network segment serving the Brocade ASCG appliance sends crafted API requests directly to the administrative management service without any credentials. Because the privileged API functions lack authentication (CWE-306), the attacker reads sensitive system configuration mapping data and modifies managed device inventories and operational settings. No public exploit code has been identified at time of analysis, and the low attack complexity (AC:L) means a working request would require little tailoring once the service is reachable. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Unauthenticated API access in Brocade ASCG (Active Support Connectivity Gateway) before version 3.5.0 lets an attacker on an adjacent network perform privileged administrative actions - reading sensitive system configuration mapping data, modifying managed device inventories, and changing operational settings - without presenting any credentials. The flaw is scored CVSS 8.7 (CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L) and is rooted in CWE-306, a missing authentication check for a critical function; no public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (no CISA KEV listing). The dominant constraint is reachability rather than skill: the attacker must be able to route to the ASCG administrative management/API interface from an adjacent or logically local segment, so deployments that place the appliance behind segmentation or firewalls are materially less exposed.
RemediationAI
The primary fix is to upgrade Brocade ASCG to version 3.5.0 or later, the first release in which the missing authentication check on the administrative API is addressed; the vendor advisory at https://support.broadcom.com/external/content/SecurityAdvisories/0/38388 should be consulted for the exact build and installation procedure before scheduling the upgrade. Until the appliance can be patched - and as a permanent hardening measure afterward - restrict network reachability to the ASCG management interface: apply firewall or ACL rules that permit access only from a dedicated management VLAN or a small set of jump hosts, since the CVSS 4.0 vector's AV:A metric makes adjacent-network reachability the single precondition an attacker must satisfy. Because the flaw is a missing authentication check in the API itself, this is the most effective available compensating control, but note the trade-off: over-restrictive rules can interrupt the outbound support-connectivity and telemetry functions that define the product, so the inbound management path should be narrowed while outbound service connectivity is preserved. Where the deployment permits it, disabling or unbinding the administrative API from any non-management interface reduces exposure further, at the cost of losing browser-based or scripted remote administration. Network-level detection should focus on API requests to the ASCG management service that arrive without a preceding authentication exchange or from unexpected source addresses, since such requests are the direct signature of this weakness; log review and alerting give visibility but do not block the action. Do not rely on TLS termination, a reverse proxy, or a WAF as a substitute for the patch, because none of these components validate ASCG-specific authorization and an attacker who can route to the backend still reaches the unauthenticated function.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Brocade Active Support Connectivity Gateway (ASCG) is a support-connectivity appliance that brokers telemetry and device-inventory data between managed Brocade infrastructure and vendor support services; its administrative management service exposes an HTTP-style API used to read configuration mappings, enumerate and edit the managed device inventory, and adjust operational settings. CWE-306 (Missing Authentication for Critical Function) is the root cause class here: the affected API endpoints perform privileged operations without validating that the caller has authenticated at all. The CPE string cpe:2.3:a:brocade:brocade_active_support_connectivity_gateway:*:*:*:*:*:*:*:* uses a wildcard version, consistent with the vendor statement that every release prior to 3.5.0 is affected rather than a single build. The CVSS 4.0 vector's AV:A metric places the attack surface on an adjacent network, PR:N confirms no authentication is required and UI:N confirms no victim interaction, while the unchanged scope (SC:N/SI:N/SA:N in 4.0, S:U in the independent 3.1 assessment) indicates the impact is confined to the ASCG appliance itself rather than chaining into downstream devices. Confidentiality and integrity impacts are high because configuration mappings and device inventories can be read and rewritten; availability impact is low, reflecting limited disruptive capability. The reference is tagged Authentication Bypass, which is the practical exploitation pattern - a caller reaching the API is treated as trusted and can act without any prior credential exchange.
Know when Brocade Active Support Connectivity Gateway gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N
Adjacent-network reach (AV:A) to an unauthenticated privileged API (PR:N, AC:L, UI:N) yields high confidentiality and integrity impact with only low availability impact; scope unchanged.
Primary rating from Vendor (brocade).
CVSS VectorVendor: brocade
Lifecycle Timeline
2DescriptionCVE.org
An authentication flaw exists in the Brocade ASCG administrative management service component. An unauthenticated network user can issue direct API requests to perform privileged actions, including accessing sensitive system configuration mapping data, modifying managed device inventories, and altering operational settings. This vulnerability affects all versions of Brocade ASCG before 3.5.0.
Executive ViewAI
Brocade ASCG (Active Support Connectivity Gateway) appliances running versions below 3.5.0 expose an unauthenticated API that lets anyone with network reach to the management interface read sensitive configuration mapping data and alter managed device inventories and operational settings. Exploitation requires only adjacency to the gateway's management segment, not credentials or specialized tooling, so exposure scales with how loosely that interface is segmented. Leadership should treat this as a network-integrity and data-confidentiality risk to supported infrastructure, particularly where ASCG sits on shared or flat internal segments, and should note that no vendor-released patch has been identified at time of analysis, leaving mitigation dependent on network controls.
No vendor-released patch identified at time of analysis - interim mitigations are network-based: enforce deny-by-default firewall/ACL rules and segmentation so only authorized management hosts can route to the ASCG administrative/API interface, isolate ASCG on a dedicated management VLAN with no path from user or partner segments, disable or block the management interface where remote access is not operationally required, enable audit logging and alerting for administrative and API actions, monitor device inventories and configuration mapping data for unauthorized modification, and rotate any credentials or secrets potentially exposed through accessible configuration data until a vendor fix is available.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Brocade Active Support Connectivity Gateway versions up to 3.4.0 contains a vulnerability that allows attackers to an un
Unauthenticated control-plane takeover in the Brocade Active Support Connectivity Gateway (ASCG) HTTPS service allows a
Authenticated code injection in Brocade ASCG before 3.5.0 allows network-adjacent attackers with low-privilege accounts
Missing authentication in the Brocade ASCG data collector API endpoint allows an unauthenticated adjacent-network attack
Path traversal in the HTTP service component of Brocade Active Support Connectivity Gateway (ASCG) before 3.5.0 allows a
Authentication bypass in Brocade ASCG versions prior to 3.5.0 allows unauthenticated attackers on an adjacent network to
Weak cryptography in Brocade Active Support Connectivity Gateway (ASCG) versions prior to 3.3.0 exposes local communicat
Brocade Active Support Connectivity Gateway (ASCG) builds prior to 3.5.0 embed a static cryptographic key inside shipped
Local credential theft in Brocade ASCG before 3.5.0 allows a low-privileged authenticated user on the ASCG VM to extract
Path traversal in Brocade Active Support Connectivity Gateway (ASCG) before 3.5.0 lets an unauthenticated attacker write
Unauthenticated attackers with adjacent-network reachability can push an unauthorized Certificate Authority certificate
JSON Web Token exposure in Brocade Active Support Connectivity Gateway (ASCG) prior to version 3.3.0 enables high-privil
EUVD-2026-94792
GHSA-548v-qvj9-7pvf
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB