Vulnerabilities

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…

An unauthenticated network-based attacker can query specific internal management endpoints on Brocade ASCG versions before 3.5.0 to enumerate the configuration details and state of managed Brocade Fabric OS (FOS) switche…

An unauthenticated remote attacker can modify the TLS client trust store in Brocade ASCG versions before 3.5.0.

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.

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 authentication flaw exists in the Brocade ASCG administrative management service component.

Brocade ASCG before 3.5.0 has a well-known Brocade default password embedded in a script distributed to every customer.

A path traversal vulnerability exists in the HTTP service component of Brocade ASCG versions before 3.5.0.

Brocade ASCG before 3.5.0 improperly processes user input by evaluating form data prior to validation.

A vulnerability has been identified in the data collection service of Brocade ASCG versions before 3.5.0.

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 communicat…

A critical security vulnerability has been identified in Brocade ASCG versions before 3.5.0.