Brocade Sannav Broadcom Brocade Sannav

Do you want an email whenever new security vulnerabilities are reported in Broadcom Brocade Sannav?

By the Year

In 2022 there have been 2 vulnerabilities in Broadcom Brocade Sannav with an average score of 9.3 out of ten. Last year Brocade Sannav had 3 security vulnerabilities published. If vulnerabilities keep coming in at the current rate, it appears that number of security vulnerabilities in Brocade Sannav in 2022 could surpass last years number. However, the average CVE base score of the vulnerabilities in 2022 is greater by 1.93.

Year Vulnerabilities Average Score
2022 2 9.30
2021 3 7.37
2020 0 0.00
2019 6 7.08
2018 0 0.00

It may take a day or so for new Brocade Sannav vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.

Recent Broadcom Brocade Sannav Security Vulnerabilities

By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters

CVE-2022-23305 9.8 - Critical - January 18, 2022

By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.

SQL Injection

JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to

CVE-2022-23302 8.8 - High - January 18, 2022

JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.

Marshaling, Unmarshaling

Brocade SANnav before v.2.1.0a could

CVE-2020-15379 7.5 - High - June 09, 2021

Brocade SANnav before v.2.1.0a could allow remote attackers cause a denial-of-service condition due to a lack of proper validation, of the length of user-supplied data as name for custom field name.

Improper Input Validation

The host SSH servers of Brocade Fabric OS before Brocade Fabric OS v7.4.2h, v8.2.1c, v8.2.2, v9.0.0, and Brocade SANnav before v2.1.1 utilize keys of less than 2048 bits

CVE-2020-15387 7.4 - High - June 09, 2021

The host SSH servers of Brocade Fabric OS before Brocade Fabric OS v7.4.2h, v8.2.1c, v8.2.2, v9.0.0, and Brocade SANnav before v2.1.1 utilize keys of less than 2048 bits, which may be vulnerable to man-in-the-middle attacks and/or insecure SSH communications.

Inadequate Encryption Strength

Brocade SANnav before version 2.1.1 uses a hard-coded administrator account with the weak password passw0rd if a password is not provided for PostgreSQL at install-time.

CVE-2020-15382 7.2 - High - June 09, 2021

Brocade SANnav before version 2.1.1 uses a hard-coded administrator account with the weak password passw0rd if a password is not provided for PostgreSQL at install-time.

Use of Hard-coded Credentials

A vulnerability, in Brocade SANnav versions before v2.0, could allow remote attackers to brute-force a valid session ID

CVE-2019-16205 8.8 - High - November 08, 2019

A vulnerability, in Brocade SANnav versions before v2.0, could allow remote attackers to brute-force a valid session ID. The vulnerability is due to an insufficiently random session ID for several post-authentication actions in the SANnav portal.

Use of Insufficiently Random Values

The authentication mechanism, in Brocade SANnav versions before v2.0, logs plaintext account credentials at the trace and the 'debug' logging level; which could

CVE-2019-16206 5.5 - Medium - November 08, 2019

The authentication mechanism, in Brocade SANnav versions before v2.0, logs plaintext account credentials at the trace and the 'debug' logging level; which could allow a local authenticated attacker to access sensitive information.

Insertion of Sensitive Information into Log File

Brocade SANnav versions before v2.0 use a hard-coded password, which could

CVE-2019-16207 7.8 - High - November 08, 2019

Brocade SANnav versions before v2.0 use a hard-coded password, which could allow local authenticated attackers to access a back-end database and gain privileges.

Use of Hard-coded Credentials

Password-based encryption (PBE) algorithm, of Brocade SANnav versions before v2.0, has a weakness in generating cryptographic keys

CVE-2019-16208 7.5 - High - November 08, 2019

Password-based encryption (PBE) algorithm, of Brocade SANnav versions before v2.0, has a weakness in generating cryptographic keys that may allow an attacker to decrypt passwords used with several services (Radius, TACAS, etc.).

Use of a Broken or Risky Cryptographic Algorithm

A vulnerability, in The ReportsTrustManager class of Brocade SANnav versions before v2.0, could

CVE-2019-16209 7.4 - High - November 08, 2019

A vulnerability, in The ReportsTrustManager class of Brocade SANnav versions before v2.0, could allow an attacker to perform a man-in-the-middle attack against Secure Sockets Layer(SSL)connections.

Improper Certificate Validation

Brocade SANnav versions before v2.0

CVE-2019-16210 5.5 - Medium - November 08, 2019

Brocade SANnav versions before v2.0, logs plain text database connection password while triggering support save.

Insertion of Sensitive Information into Log File

Stay on top of Security Vulnerabilities

Want an email whenever new vulnerabilities are published for Broadcom Brocade Sannav or by Broadcom? Click the Watch button to subscribe.

Broadcom
Vendor

subscribe