Brocade SANnav: Incorrect Default Permissions
CVE-2024-2859 is a high-severity incorrect default permissions vulnerability in Brocade SANnav from Brocade, with a CVSS 3.1 base score of 7.2 out of 10. It can be exploited remotely over the network by an attacker with administrator privileges, without any action from a user. Affected Brocade SANnav versions: v2.3.0. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.85% chance of exploitation within 30 days, higher than 59% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Brocade SANnav you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on support.broadcom.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Brocade | Brocade SANnav | v2.3.0 | Not stated |
| Broadcom | brocade_sannav | 2.3.0 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- HighAdministrator-level access is required first.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 6.8 | Medium | CNA (brocade.com) |
| CVSS 3.1 | 7.2 | High | NVD |
Official description
By default, SANnav OVA is shipped with root user login enabled. While protected by a password, access to root could expose SANnav to a remote attacker should they gain access to the root account.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Incorrect Default Permissions
During installation, installed file permissions are set to allow anyone to modify those files.
How developers prevent this class of flaw
- The architecture needs to access and modification attributes for files to only those users who actually require those actions.
- Compartmentalize the system to have safe areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
More Incorrect Default Permissions vulnerabilities (CWE-276)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- security.netapp.com/advisory/ntap-20240628-0003/Third Party Advisory
Other vulnerabilities in Brocade SANnav
- 8.0 High severity
- 7.2 High severity
- 7.8 High severity
- 9.8 Critical severity
- 7.5 High severity
- 7.5 High severity
Recent Incorrect Default Permissions vulnerabilities
- 7.5 High severity
- 7.8 High severity
- 7.8 High severity
- 9.8 Critical severity
- 8.8 High severity
- 7.8 High severity
Spotted an error? Tell us.