Skip to content
OpenAdvisories
High WID-SEC-2024-0915 10 CVEs

Broadcom Brocade SANnav: Mehrere Schwachstellen

Published Apr 16, 2024 · Updated Oct 14, 2024 · Revision 2 · de-DE

Summary

Ein Angreifer kann mehrere Schwachstellen in Broadcom Brocade SANnav ausnutzen, um einen Denial of Service Angriff durchzuführen oder vertrauliche Informationen offenlegen.

Product

Brocade SANnav ist eine Managementlösung für Storage Area Networks (SAN).

Vulnerabilities 10

  • High 8.6

    Brocade Fabric OS switch encrypted passwords in the Brocade SANnav Standby node's support save

    A vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a prints Brocade Fabric OS switch encrypted passwords in the Brocade SANnav Standby node's support save.

  • High 8.2

    supply-chain attack risk

    A vulnerability affects Brocade SANnav before v2.3.1 and v2.3.0a. It allows a Brocade SANnav service to send ping commands in the background at regular intervals to gridgain.com to check if updates are available for the Component. This could make an unauthent…

  • High 7.7

    SQL Table names, column names, and SQL queries are collected in DR standby Supportsave

    An information disclosure vulnerability exists in Brocade SANnav before v2.3.1 and v2.3.0a when Brocade SANnav instances are configured in disaster recovery mode. SQL Table names, column names, and SQL queries are collected in DR standby Supportsave. This cou…

  • High 7.5

    Apache Avro Java SDK: Memory when deserializing untrusted data in Avro Java SDK

    When deserializing untrusted or corrupted data, it is possible for a reader to consume memory beyond the allowed constraints and thus lead to out of memory on the system. This issue affects Java applications using Apache Avro Java SDK up to and including 1.11…

  • High 7.5

    Encryption key in the console when a privileged user executes the script to replace the Brocade SANnav Management Portal standby node.

    A vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a prints the encryption key in the console when a privileged user executes the script to replace the Brocade SANnav Management Portal standby node. This could provide attackers an additional, less prot…

  • High 7.5

    TLS/SSL weak message authentication code ciphers are added by default for port 18082

    When a Brocade SANnav installation is upgraded from Brocade SANnav v2.2.2 to Brocade SANnav 2.3.0, TLS/SSL weak message authentication code ciphers are added by default for port 18082.

  • Medium 6.8

    Identical SSH keys utilized inside the OVA image (CVE-2024-29960)

    In Brocade SANnav server before v2.3.1 and v2.3.0a, the SSH keys inside the OVA image are identical in the VM every time SANnav is installed. Any Brocade SAnnav VM based on the official OVA images is vulnerable to MITM over SSH. An attacker can decrypt and co…

  • Medium 5.5

    Clear text storage of sensistive information by manipulating command variables

    A vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a could allow an authenticated user to print the Auth, Priv, and SSL key store passwords in unencrypted logs by manipulating command variables.

  • Medium 5.0

    Insertion of Sensitive Information into Brocade SANnav Log File

    A vulnerability in Brocade SANnav before v2.3.1 and v2.3.0a could allow a privileged user to print the SANnav encrypted key in PostgreSQL startup logs. This could provide attackers with an additional, less-protected path to acquiring the encryption key.

  • Low 1.9

    Brocade SANnav contains hardcoded TLS keys used by Docker

    Brocade SANnav OVA before v2.3.1, and v2.3.0a, contain hardcoded TLS keys used by Docker. Note: Brocade SANnav doesn't have access to remote Docker registries.

Revision history

  1. #2

    Neue Updates aufgenommen

  2. #1

    Initiale Fassung

References