Brocade Vulnerabilities

Timeline

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

Type

The moderation team is working with the threat intelligence team to categorize software that is affected by security vulnerabilities. This helps to illustrate the assignment of these categories to determine the most affected software types.

Product

Brocade Fabric OS66
Brocade SANnav47
Brocade Network Advisor8
Brocade SANNav3
Brocade Vyatta 5400 Vrouter Software3

Grouping vulnerabilities by products helps to get an overview. This makes it possible to determine an homogeneous landscape or the most important hotspots in heterogeneous landscapes.

Remediation

Official Fix121
Temporary Fix0
Workaround3
Unavailable0
Not Defined17

Vendors and researchers are eager to find countermeasures to mitigate security vulnerabilities. These can be distinguished between multiple forms and levels of remediation which influence risks differently.

Exploitability

High1
Functional1
Proof-of-Concept3
Unproven1
Not Defined135

Researcher and attacker which are looking for security vulnerabilities try to exploit them for academic purposes or personal gain. The level and quality of exploitability can be distinguished to determine simplicity and strength of attacks.

Access Vector

Not Defined0
Physical0
Local39
Adjacent28
Network74

The approach a vulnerability it becomes important to use the expected access vector. This is typically via the network, local, or physically even.

Authentication

Not Defined0
High6
Low78
None57

To exploit a vulnerability a certail level of authentication might be required. Vulnerabilities without such a requirement are much more popular.

User Interaction

Not Defined0
Required9
None132

Some attack scenarios require some user interaction by a victim. This is typical for phishing, social engineering and cross site scripting attacks.

C3BM Index

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

CVSSv3 Base

≤10
≤20
≤31
≤415
≤518
≤631
≤738
≤825
≤912
≤101

The Common Vulnerability Scoring System (CVSS) is an industry standard to define the characteristics and impacts of security vulnerabilities. The base score represents the intrinsic aspects that are constant over time and across user environments. Our unique meta score merges all available scores from different sources to aggregate to the most reliable result.

CVSSv3 Temp

≤10
≤20
≤33
≤413
≤520
≤642
≤726
≤825
≤911
≤101

The Common Vulnerability Scoring System (CVSS) uses temp scores to reflect the characteristics of a vulnerability that may change over time but not across user environments. This includes reporting confidence, exploitability and remediation levels. We do also provide our unique meta score for temp scores, even though other sources rarely publish them.

VulDB

≤10
≤20
≤38
≤432
≤519
≤630
≤723
≤824
≤93
≤102

The moderation team is always defining the base vector and base score for an entry. These and all other available scores are used to generate the meta score.

NVD

≤10
≤20
≤30
≤40
≤51
≤69
≤79
≤826
≤910
≤1011

The National Vulnerability Database (NVD) is also defining CVSS vectors and scores. These are usually not complete and might differ from VulDB scores.

CNA

≤10
≤20
≤30
≤40
≤57
≤612
≤76
≤813
≤98
≤101

A CVE Numbering Authority (CNA) is responsible for assigning new CVE entries. They might also include a CVSS score. These are usually not complete and might differ from VulDB scores.

Vendor

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

Some vendors are willing to publish their own CVSS vectors and scores for vulnerabilities in their products. The coverage varies from vendor to vendor.

Research

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

There are sometimes also security researcher which provide their own CVSS vectors and scores for vulnerabilities they have found and published.

Exploit 0-day

<1k44
<2k67
<5k30
<10k0
<25k0
<50k0
<100k0
≥100k0

The moderation team is working with the threat intelligence team to determine prices for exploits. Our unique algorithm is used to identify the 0-day prices for an exploit, before it got distributed or became public. Calculated prices are aligned to prices disclosed by vulnerability broker and compared to prices we see on exploit markets.

Exploit Today

<1k136
<2k5
<5k0
<10k0
<25k0
<50k0
<100k0
≥100k0

The 0-day prices do not consider time-relevant factors. The today price does reflect price impacts like disclosure of vulnerability details, alternative exploits, availability of countermeasures. These dynamic aspects might decrease the exploit prices over time. Under certain circumstances this happens very fast.

Exploit Market Volume

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

🔴 CTI Activities

Our unique Cyber Threat Intelligence aims to determine the ongoing research of actors to anticipiate their acitivities. Observing exploit markets on the Darknet, discussions of vulnerabilities on mailinglists, and exchanges on social media makes it possible to identify planned attacks. Monitored actors and activities are classified whether they are offensive or defensive. They are also weighted as some actors are well-known for certain products and technologies. And some of their disclosures might contain more or less details about technical aspects and personal context. The world map highlights active actors in real-time.

Affected Products (19): BigIron RX switch (1), Bigiron (1), Fabric (1), Fabric OS (66), Fastiron (1), Fibre Channel SAN (2), NetIron (1), NetIron MLX Line Card (1), Netiron (1), Network Advisor (8), SANNav (3), SANnav (47), SAnnav (1), ServerIron ADX Switches (3), Silkworm (1), Turboiron (1), Virtual Traffic Manager (1), Vyatta 5400 Vrouter Software (3), Vyatta vRouter (1)

PublishedBaseTempVulnerabilityProdExpRemEPSSCTICVE
06/26/20244.34.2Brocade Fabric OS Web Interface sensitive informationUnknownNot DefinedOfficial Fix0.000430.04CVE-2024-29953
06/26/20244.34.3Brocade Fabric OS Password Management API log fileUnknownNot DefinedOfficial Fix0.000430.00CVE-2024-29954
06/26/20246.26.1Brocade Fabric OS SNMP hard-coded credentialsUnknownNot DefinedOfficial Fix0.000430.09CVE-2024-5460
05/08/20247.87.6Brocade SAnnav PostgreSQL Database missing authenticationUnknownNot DefinedOfficial Fix0.000430.04CVE-2024-2860
04/27/20246.86.8Brocade SANnav access controlUnknownNot DefinedNot Defined0.000430.05CVE-2024-2859
04/25/20248.38.2Brocade SANnav Kafka access controlUnknownNot DefinedOfficial Fix0.000430.03CVE-2024-4173
04/25/20246.16.1Brocade SANnav syslog cleartext transmissionUnknownNot DefinedOfficial Fix0.000430.03CVE-2024-4161
04/25/20246.46.3Brocade SANnav Kafka API information disclosureUnknownNot DefinedOfficial Fix0.000430.06CVE-2024-4159
04/19/20246.46.3Brocade SANnav Message Authentication Code inadequate encryptionUnknownNot DefinedOfficial Fix0.000430.00CVE-2024-29969
04/19/20246.05.9Brocade SANnav Disaster Recovery Mode information disclosureUnknownNot DefinedOfficial Fix0.000430.03CVE-2024-29968
04/19/20243.33.3Brocade SANnav Docker default permissionUnknownNot DefinedOfficial Fix0.000430.05CVE-2024-29967
04/19/20246.96.8Brocade SANnav Standby Node Support Save log fileUnknownNot DefinedOfficial Fix0.000430.03CVE-2024-29959
04/19/20245.55.4Brocade SANnav SSH sensitive informationUnknownNot DefinedOfficial Fix0.000430.03CVE-2024-29965
04/19/20244.44.3Brocade SANnav default permissionUnknownNot DefinedOfficial Fix0.000430.03CVE-2024-29962
04/19/20243.83.7Brocade SANnav Docker Daemon information disclosureUnknownNot DefinedOfficial Fix0.000430.00CVE-2024-29964
04/19/20246.46.3Brocade SANnav Console log fileUnknownNot DefinedOfficial Fix0.000430.06CVE-2024-29958
04/19/20246.46.3Brocade SANnav Disaster Recovery Mode log fileUnknownNot DefinedOfficial Fix0.000430.03CVE-2024-29957
04/19/20248.78.5Brocade SANnav hard-coded credentialsUnknownNot DefinedOfficial Fix0.000430.04CVE-2024-29966
04/19/20246.46.3Brocade SANnav OVA Image hard-coded credentialsUnknownNot DefinedOfficial Fix0.000430.03CVE-2024-29960
04/19/20246.76.6Brocade SANnav Service information disclosureUnknownNot DefinedOfficial Fix0.000430.04CVE-2024-29961
04/19/20246.16.1Brocade SANnav TLS Connection hard-coded keyUnknownNot DefinedOfficial Fix0.000430.04CVE-2024-29963
04/18/20245.45.3Brocade SANnav supportsave Log log fileUnknownNot DefinedOfficial Fix0.000430.03CVE-2024-29956
04/18/20243.93.8Brocade SANnav PostgreSQL log fileUnknownNot DefinedOfficial Fix0.000430.09CVE-2024-29955
04/17/20244.44.3Brocade SANnav log fileUnknownNot DefinedOfficial Fix0.000430.03CVE-2024-29952
04/17/20244.14.1Brocade SANnav Internal SSH Port inadequate encryptionUnknownNot DefinedOfficial Fix0.000430.03CVE-2024-29951

116 more entries are not shown

Do you know our Splunk app?

Download it now for free!