Brocade Active Support Connectivity Gateway vulnerabilities
10 known vulnerabilities in Brocade Active Support Connectivity Gateway from Brocade. 10 are rated high or critical. Each entry lists the affected versions and the release that fixes it, where the vendor has published one.
Latest first
- 7.8 High severity
Brocade Active Support Connectivity Gateway: Insufficiently Protected Credentials
In Brocade ASCG before 3.5.0, a local unauthorized user on the ASCG VM who can issue a request to the SANnav host network namespace can extract stored management credentials for onboarded SANnav instances and compromise connected Brocade SANnav servers or mana
- 8.8 High severity
Brocade Active Support Connectivity Gateway: Use of Hard-coded Cryptographic Key
A vulnerability in the SupportLink API authentication component of Brocade ASCG versions prior to 3.5.0 allows an attacker to bypass authentication across deployments due to the use of a hard coded cryptographic key.
- 8.8 High severity
Brocade Active Support Connectivity Gateway: Improper Limitation of a Pathname to a Restricted Directory
When Brocade ASCG before 3.5.0 processes support bundle archives ingested from remote compromised endpoints, the application fails to sanitize path traversal sequences contained within archive entries prior to extraction. An unauthenticated remote attacker cap
- 8.8 High severity
Brocade Active Support Connectivity Gateway: Missing Authentication for Critical Functionality
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, modifyi
- 7.8 High severity
Brocade Active Support Connectivity Gateway: Use of Hard-coded Credentials
Brocade ASCG before 3.5.0 has a well-known Brocade default password embedded in a script distributed to every customer. Any local authenticated user with read access to the installation path can discover this credential and perform privilege escalation on affe
- 8.8 High severity
Brocade Active Support Connectivity Gateway: Improper Limitation of a Pathname to a Restricted Directory
A path traversal vulnerability exists in the HTTP service component of Brocade ASCG versions before 3.5.0. An unauthenticated attacker on the local network could send a manipulated API request to the service endpoint bypassing path restrictions to arbitrary fi
- 8.0 High severity
Brocade Active Support Connectivity Gateway: Improper Neutralization of Directives in Dynamically Evaluated Code
Brocade ASCG before 3.5.0 improperly processes user input by evaluating form data prior to validation. When an authenticated user submits a configuration form, the submitted text could immediately be processed. A malicious actor with basic access can supply cr
- 8.8 High severity
Brocade Active Support Connectivity Gateway: Missing Authentication for Critical Functionality
A vulnerability has been identified in the data collection service of Brocade ASCG versions before 3.5.0. An API endpoint within the data collector service fails to perform authentication or authorization checks on incoming requests. An attacker with network a
- 7.8 High severity
Brocade Active Support Connectivity Gateway: Use of Hard-coded Credentials
A vulnerability in Brocade ASCG version before 3.5.0 could allow an attacker to obtain a static cryptographic key hardcoded into the software binaries to secure sensitive data at rest and to protect inter-node communication protocols. An attacker who extracts
- 8.8 High severity
Brocade Active Support Connectivity Gateway: Missing Authentication for Critical Functionality
A critical security vulnerability has been identified in Brocade ASCG versions before 3.5.0. The HTTPS service fails to properly enforce authentication or access control checks on incoming requests. An unauthenticated attacker with network access can issue con