Sannav
Monthly
Incomplete log sanitization in Brocade SANnav before 3.0.1a causes extension switch IPsec pre-shared keys (PSKs) to be written in cleartext to system logs during the bulk IPsec policy collection workflow, allowing any principal with read access to container logs or exported support archives to recover those keys and potentially compromise the IPsec-protected tunnels that rely on them. The issue is local and authenticated (CVSS 3.1 AV:L/AC:L/PR:L/UI:N, confidentiality-only per independent assessment), not remotely reachable, and it is tied specifically to that diagnostic collection path rather than to arbitrary attacker input; no public exploit code has been identified at time of analysis. The 8.4 CVSS 4.0 vendor score (which also asserts high integrity impact via VI:H) should not be used as the sole triage signal, since the practical outcome depends on the attacker both holding log/support-bundle read privileges and being able to reach and reuse the leaked PSKs against the switch fabric.
Pre-shared keys used for IPsec tunnel configuration are recorded in cleartext inside application log files by Brocade SANnav versions before 3.0.1a, so anyone who can read those logs or an exported support bundle can recover credentials that protect network tunnels. The exposure is triggered only when IPsec policies are actually created or modified in SANnav, and the assessed vector (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) reflects a local, authenticated precondition rather than anonymous remote reach, meaning an insider or a holder of an exported bundle is the realistic actor. There is no public exploit identified at time of analysis and the issue is not in CISA KEV, so priority should be driven by the sensitivity of the logged keys and by how broadly log files and support bundles are shared; the vendor has addressed it in 3.0.1a.
Plaintext disclosure of administrative switch credentials and live session tokens in Brocade SANnav discovery-service log files lets anyone who can read those logs - or who is handed an exported support bundle - recover credentials that unlock the managed SAN fabric. All SANnav releases before 3.0.1a are affected, and the logging occurs under default configuration, so the only barrier is obtaining local read access to the log directory or bundle; the CVSS v3.1 assessment (8.5, AV:L/AC:L/PR:L/UI:N, C/I/A:H) and the vendor-published CVSS v4.0 vector (8.5) both place this at high severity because a successful read escalates into full compromise of managed switches and active user sessions. Exploitation is access-gated rather than remote or unauthenticated, and no public exploit identified at time of analysis; there is no CISA KEV listing for this CVE. Actual fabric compromise is a second step contingent on the disclosed credentials still being valid and the switches being reachable.
Command injection in the Brocade SANnav CLI scripting component lets an authenticated user who already holds command-execution/scripting permissions break out of the restricted allow-list execution context and run unauthorized shell commands across managed fabric switches, escalating to full administrative switch access. Exploitation requires a valid SANnav account with scripting rights and adjacency to the SAN management plane (AV:A, PR:L) - the product is not internet-reachable by default - and no user interaction is needed once that foothold exists. Every SANnav release before 3.0.1a is in scope per the CPE (cpe:2.3:a:brocade:sannav:*:*:*:*:*:*:*:*), and no public exploit code has been identified at time of analysis; this is a genuine mid-to-high priority for SANnav operators, not an emergency-tier internet-facing issue.
Brocade SANnav deployments running versions before 3.0.1a expose backend management service ports without adequate access controls, so a local, non-administrative user on the SANnav host can talk directly to those services and relay commands to interconnected Fabric OS switches under the SANnav management user's identity. Exploitation is access-gated: it requires an authenticated low-privileged account on the host (PR:L, consistent across both the vendor CVSS 4.0 vector and our assessed CVSS:3.1 vector AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) plus a SANnav instance that is actively managing switches, but where those conditions hold, impact is high across confidentiality, integrity and availability with a changed scope because the attacker's authority crosses from the host user into the managed switch fabric. No public exploit code or confirmed active exploitation was identified at time of analysis.
Incomplete property masking in Brocade SANnav's logging subsystem can cause SNMP authentication and privacy passwords to be written into application logs whenever specific configuration conditions are met, so anyone who can read those logs or a generated support bundle can recover the credentials and use them for unauthorized read or management access to the monitored switch environment. The flaw is not remotely exploitable by an unauthenticated attacker: per the available CVSS data (PR:L) and our independent assessment (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N), exploitation requires an actor who already holds log or support-bundle read privileges, and the sensitive values only appear under non-universal configuration conditions. No public exploit code and no confirmed active exploitation were identified at time of analysis; the practical risk is a credential-hygiene and information-disclosure exposure realized by insiders or by a post-compromise actor who reuses the recovered SNMP credentials against reachable switches.
Cleartext credential exposure in the job scheduling component of Brocade SANnav causes external server passwords and archive protection keys to be written unmasked into application logs and generated support bundles whenever scheduled support-save or related operational jobs execute. An authenticated, low-privileged user who already has read access to those logs or bundles can harvest the credentials and potentially reuse them against remote backup targets or protected archives. This is a confidentiality-only defect rooted in improper log masking (CWE-532), with no public exploit identified at time of analysis; practical impact is LOW-priority because the attacker must already hold log access and the secrets are only exposed after an affected job has actually run.
A vulnerability in the migration script for Brocade SANnav before 3.0 could allow the collection of database sql queries in the SANnav support save file. [CVSS 7.5 HIGH]
A vulnerability in update-reports-purge-settings.sh script logging for Brocade SANnav before 2.4.0a could allow the collection of SANnav database password in the system audit logs. [CVSS 6.5 MEDIUM]
Brocade SANnav before 2.4.0b logs the Brocade Fabric OS Switch admin password on the SANnav support save logs. When OOM occurs on a Brocade SANnav server, the call stack trace for the Brocade switch is also collected in the heap dump file which contains this switch password in clear text. [CVSS 4.9 MEDIUM]
Sannav contains a vulnerability that allows attackers to a remote authenticated attacker with admin privilege able to access the SANnav l (CVSS 4.9).
A vulnerability in Brocade SANnav before 2.4.0b prints the Password-Based Encryption (PBE) key in plaintext in the system audit log file. The vulnerability could allow a remote authenticated attacker with access to the audit logs to access the pbe key. [CVSS 6.5 MEDIUM]
In Brocade SANnav before Brocade SANnav v2.2.0.2 and Brocade SANnav2.1.1.8, encoded scp-server passwords are stored using Base64 encoding, which could allow an attacker able to access log files to. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
Brocade SANnav before Brocade SANvav v. Rated medium severity (CVSS 6.5), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
In Brocade SANnav version before SANN2.2.0.2 and Brocade SANNav before 2.1.1.8, the implementation of TLS/SSL Server Supports the Use of Static Key Ciphers (ssl-static-key-ciphers) on ports 443 &. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
In addition to the c_rehash shell command injection identified in CVE-2022-1292, further circumstances where the c_rehash script does not properly sanitise shell metacharacters to prevent command. Rated high severity (CVSS 7.3), this vulnerability is low attack complexity. This OS Command Injection vulnerability could allow attackers to execute arbitrary operating system commands on the host.
Brocade SANnav before version SANnav 2.2.0 logs the REST API Authentication token in plain text. Rated low severity (CVSS 3.3), this vulnerability is low attack complexity. No vendor patch available.
An information exposure through log file vulnerability in Brocade SANNav versions before Brocade SANnav 2.2.0 could allow an authenticated, local attacker to view sensitive information such as ssh. Rated medium severity (CVSS 5.5), this vulnerability is low attack complexity. No vendor patch available.
A vulnerability in the role-based access control (RBAC) functionality of the Brocade SANNav before 2.2.0 could allow an authenticated, remote attacker to access resources that they should not be able. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
Brocade SANnav before SANnav 2.2.0 application uses the Blowfish symmetric encryption algorithm for the storage of passwords. Rated medium severity (CVSS 6.5), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
In Brocade SANnav before Brocade SANnav 2.2.0, multiple endpoints associated with Zone management are susceptible to SQL injection, allowing an attacker to run arbitrary SQL commands. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
An issue was discovered in Docker Engine before 19.03.11. Rated medium severity (CVSS 6.0), this vulnerability is remotely exploitable. No vendor patch available.
Incomplete log sanitization in Brocade SANnav before 3.0.1a causes extension switch IPsec pre-shared keys (PSKs) to be written in cleartext to system logs during the bulk IPsec policy collection workflow, allowing any principal with read access to container logs or exported support archives to recover those keys and potentially compromise the IPsec-protected tunnels that rely on them. The issue is local and authenticated (CVSS 3.1 AV:L/AC:L/PR:L/UI:N, confidentiality-only per independent assessment), not remotely reachable, and it is tied specifically to that diagnostic collection path rather than to arbitrary attacker input; no public exploit code has been identified at time of analysis. The 8.4 CVSS 4.0 vendor score (which also asserts high integrity impact via VI:H) should not be used as the sole triage signal, since the practical outcome depends on the attacker both holding log/support-bundle read privileges and being able to reach and reuse the leaked PSKs against the switch fabric.
Pre-shared keys used for IPsec tunnel configuration are recorded in cleartext inside application log files by Brocade SANnav versions before 3.0.1a, so anyone who can read those logs or an exported support bundle can recover credentials that protect network tunnels. The exposure is triggered only when IPsec policies are actually created or modified in SANnav, and the assessed vector (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) reflects a local, authenticated precondition rather than anonymous remote reach, meaning an insider or a holder of an exported bundle is the realistic actor. There is no public exploit identified at time of analysis and the issue is not in CISA KEV, so priority should be driven by the sensitivity of the logged keys and by how broadly log files and support bundles are shared; the vendor has addressed it in 3.0.1a.
Plaintext disclosure of administrative switch credentials and live session tokens in Brocade SANnav discovery-service log files lets anyone who can read those logs - or who is handed an exported support bundle - recover credentials that unlock the managed SAN fabric. All SANnav releases before 3.0.1a are affected, and the logging occurs under default configuration, so the only barrier is obtaining local read access to the log directory or bundle; the CVSS v3.1 assessment (8.5, AV:L/AC:L/PR:L/UI:N, C/I/A:H) and the vendor-published CVSS v4.0 vector (8.5) both place this at high severity because a successful read escalates into full compromise of managed switches and active user sessions. Exploitation is access-gated rather than remote or unauthenticated, and no public exploit identified at time of analysis; there is no CISA KEV listing for this CVE. Actual fabric compromise is a second step contingent on the disclosed credentials still being valid and the switches being reachable.
Command injection in the Brocade SANnav CLI scripting component lets an authenticated user who already holds command-execution/scripting permissions break out of the restricted allow-list execution context and run unauthorized shell commands across managed fabric switches, escalating to full administrative switch access. Exploitation requires a valid SANnav account with scripting rights and adjacency to the SAN management plane (AV:A, PR:L) - the product is not internet-reachable by default - and no user interaction is needed once that foothold exists. Every SANnav release before 3.0.1a is in scope per the CPE (cpe:2.3:a:brocade:sannav:*:*:*:*:*:*:*:*), and no public exploit code has been identified at time of analysis; this is a genuine mid-to-high priority for SANnav operators, not an emergency-tier internet-facing issue.
Brocade SANnav deployments running versions before 3.0.1a expose backend management service ports without adequate access controls, so a local, non-administrative user on the SANnav host can talk directly to those services and relay commands to interconnected Fabric OS switches under the SANnav management user's identity. Exploitation is access-gated: it requires an authenticated low-privileged account on the host (PR:L, consistent across both the vendor CVSS 4.0 vector and our assessed CVSS:3.1 vector AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) plus a SANnav instance that is actively managing switches, but where those conditions hold, impact is high across confidentiality, integrity and availability with a changed scope because the attacker's authority crosses from the host user into the managed switch fabric. No public exploit code or confirmed active exploitation was identified at time of analysis.
Incomplete property masking in Brocade SANnav's logging subsystem can cause SNMP authentication and privacy passwords to be written into application logs whenever specific configuration conditions are met, so anyone who can read those logs or a generated support bundle can recover the credentials and use them for unauthorized read or management access to the monitored switch environment. The flaw is not remotely exploitable by an unauthenticated attacker: per the available CVSS data (PR:L) and our independent assessment (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N), exploitation requires an actor who already holds log or support-bundle read privileges, and the sensitive values only appear under non-universal configuration conditions. No public exploit code and no confirmed active exploitation were identified at time of analysis; the practical risk is a credential-hygiene and information-disclosure exposure realized by insiders or by a post-compromise actor who reuses the recovered SNMP credentials against reachable switches.
Cleartext credential exposure in the job scheduling component of Brocade SANnav causes external server passwords and archive protection keys to be written unmasked into application logs and generated support bundles whenever scheduled support-save or related operational jobs execute. An authenticated, low-privileged user who already has read access to those logs or bundles can harvest the credentials and potentially reuse them against remote backup targets or protected archives. This is a confidentiality-only defect rooted in improper log masking (CWE-532), with no public exploit identified at time of analysis; practical impact is LOW-priority because the attacker must already hold log access and the secrets are only exposed after an affected job has actually run.
A vulnerability in the migration script for Brocade SANnav before 3.0 could allow the collection of database sql queries in the SANnav support save file. [CVSS 7.5 HIGH]
A vulnerability in update-reports-purge-settings.sh script logging for Brocade SANnav before 2.4.0a could allow the collection of SANnav database password in the system audit logs. [CVSS 6.5 MEDIUM]
Brocade SANnav before 2.4.0b logs the Brocade Fabric OS Switch admin password on the SANnav support save logs. When OOM occurs on a Brocade SANnav server, the call stack trace for the Brocade switch is also collected in the heap dump file which contains this switch password in clear text. [CVSS 4.9 MEDIUM]
Sannav contains a vulnerability that allows attackers to a remote authenticated attacker with admin privilege able to access the SANnav l (CVSS 4.9).
A vulnerability in Brocade SANnav before 2.4.0b prints the Password-Based Encryption (PBE) key in plaintext in the system audit log file. The vulnerability could allow a remote authenticated attacker with access to the audit logs to access the pbe key. [CVSS 6.5 MEDIUM]
In Brocade SANnav before Brocade SANnav v2.2.0.2 and Brocade SANnav2.1.1.8, encoded scp-server passwords are stored using Base64 encoding, which could allow an attacker able to access log files to. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
Brocade SANnav before Brocade SANvav v. Rated medium severity (CVSS 6.5), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
In Brocade SANnav version before SANN2.2.0.2 and Brocade SANNav before 2.1.1.8, the implementation of TLS/SSL Server Supports the Use of Static Key Ciphers (ssl-static-key-ciphers) on ports 443 &. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
In addition to the c_rehash shell command injection identified in CVE-2022-1292, further circumstances where the c_rehash script does not properly sanitise shell metacharacters to prevent command. Rated high severity (CVSS 7.3), this vulnerability is low attack complexity. This OS Command Injection vulnerability could allow attackers to execute arbitrary operating system commands on the host.
Brocade SANnav before version SANnav 2.2.0 logs the REST API Authentication token in plain text. Rated low severity (CVSS 3.3), this vulnerability is low attack complexity. No vendor patch available.
An information exposure through log file vulnerability in Brocade SANNav versions before Brocade SANnav 2.2.0 could allow an authenticated, local attacker to view sensitive information such as ssh. Rated medium severity (CVSS 5.5), this vulnerability is low attack complexity. No vendor patch available.
A vulnerability in the role-based access control (RBAC) functionality of the Brocade SANNav before 2.2.0 could allow an authenticated, remote attacker to access resources that they should not be able. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
Brocade SANnav before SANnav 2.2.0 application uses the Blowfish symmetric encryption algorithm for the storage of passwords. Rated medium severity (CVSS 6.5), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
In Brocade SANnav before Brocade SANnav 2.2.0, multiple endpoints associated with Zone management are susceptible to SQL injection, allowing an attacker to run arbitrary SQL commands. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
An issue was discovered in Docker Engine before 19.03.11. Rated medium severity (CVSS 6.0), this vulnerability is remotely exploitable. No vendor patch available.