CVE-2026-82372: Improper handling of sensitive data during IPsec policy creation and modification in Brocade SANnav before 3.0.1.a
Improper handling of sensitive data during IPsec policy creation and modification in Brocade SANnav versions before 3.0.1a results in pre-shared keys being recorded in application logs. Individuals with read access to system log files or support bundles can view these credentials, leading to the potential exposure of keys used to secure network tunnels.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Brocade SANnavto a version that resolves this vulnerability.Fixed in 3.0.1a
Event History
Frequently Asked Questions
Who could obtain the exposed pre-shared keys?
Individuals with read access to SANnav system log files or support bundles can view the pre-shared keys recorded there. Exposure therefore depends on access to those artifacts rather than access to the IPsec policy interface alone.
When are credentials written to logs?
The issue occurs during IPsec policy creation and modification. Pre-shared keys may be recorded in application logs as part of those operations.
How can I determine whether my environment is affected?
Check whether the SANnav version is earlier than 3.0.1a and review application logs and support bundles associated with IPsec policy creation or modification for recorded pre-shared keys.
What should be done if affected logs or support bundles may have been accessed?
Treat the pre-shared keys present in those artifacts as potentially exposed, since they may secure network tunnels. Restrict access to the logs and support bundles and replace exposed keys as appropriate.