CVE Intelligence

Vulnerabilidades do Broadcom Brocade Sannav

🔔 Criar alerta RSS Verificador de versão

CVEs publicadas que afetam Broadcom Brocade Sannav: 5 registro(s), com versões afetadas e correções.
cpe:2.3:a:broadcom:brocade_sannav

CVE-2026-5769 Média · 4.1 CWE-313 08/10/2026
A vulnerability in Brocade SANnav before 3.0.1 can have the Brocade Fabric OS switch admin...
A vulnerability in Brocade SANnav before 3.0.1 can have the Brocade Fabric OS switch admin password captured in plaintext within a memory swap file on the server hosting the Brocade SANnav Virtual Machine (VM). This can happen when the SANnav server encounters an Out Of Memory (OOM) condition. The vulnerability could allow an authenticated admin user with access to the server hosting the SANnav to potentially view the memory swap file and access the password(s).
CVE-2026-5049 Média · 5.7 CWE-22 08/10/2026
A path traversal vulnerability affects the The Zone Alias Import flow feature in Brocade SANnav...
A path traversal vulnerability affects the The Zone Alias Import flow feature in Brocade SANnav before 3.0.0a. A local authenticated attacker can write an uploaded content outside the intended directory.
CVE-2026-5048 Alta · 8.0 CWE-89 08/10/2026
In Brocade SANnav before 3.0.0a, an SQL Injection vulnerability in various external API...
In Brocade SANnav before 3.0.0a, an SQL Injection vulnerability in various external API inventories have a vulnerability that allows an authenticated attacker to inject malicious data into some of the REST API -query parameters.
CVE-2026-5047 Média · 5.7 CWE-922 08/10/2026
Insecure Storage of Sensitive Information em Brocade SANnav
A vulnerability in Brocade SANnav before 2.4.0b and 3.0.0 prints encoded passwords and  authentication tokens in log files. The vulnerability could allow an authenticated attacker with access to the log file including the SANnav supportsave to access the passwords.
CVE-2024-3596 Crítica · 9.0 CWE-354 09/07/2024
RADIUS Protocol under RFC2865 is vulnerable to forgery attacks.
RADIUS Protocol under RFC 2865 is susceptible to forgery attacks by a local attacker who can modify any valid Response (Access-Accept, Access-Reject, or Access-Challenge) to any other response using a chosen-prefix collision attack against MD5 Response Authenticator signature.