Sensitive file disclosure via insecure Docker mounts
Published Apr 19, 2024 · Updated Aug 2, 2024
Incorrect default permissions in Brocade SANnav before 2.3.0a or 2.3.1 allow local users with sudo privileges to read sensitive files. Docker instances receive insecure host mount points that expose sensitive host files with read and write access. Exploitation requires sudo privilege on the Linux host; the vendor reports confidentiality impact only, with no service interruption.
Summary
What happened
Incorrect default permissions in Brocade SANnav before 2.3.0a or 2.3.1 allow local users with sudo privileges to read sensitive files. Docker instances receive insecure host mount points that expose sensitive host files with read and write access. Exploitation requires sudo privilege on the Linux host; the vendor reports confidentiality impact only, with no service interruption.
The record
- CVE
- CVE-2024-29967
- Published
- Apr 19, 2024
- Updated
- Aug 2, 2024
- Vendor
- Brocade Communications Systems
- Product
- SANnav
- Classifications
- CWE-276, CAPEC-37, T1005
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Apr 19, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.3.0a
- Affected versionversion=0 <2.3.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo