Local sensitive-data access via incorrect PostgreSQL authentication
Published May 8, 2024 · Updated Aug 1, 2024
Incorrect local authentication in PostgreSQL for Brocade SANnav before 2.3.0a allows local users to access sensitive database data. Broadcom identifies PostgreSQL as the affected component but has not published the authentication check, configuration, or credential handling that fails. Access to the SANnav virtual machine and low local privileges are required; successful exploitation exposes database contents to the local user.
Summary
What happened
Incorrect local authentication in PostgreSQL for Brocade SANnav before 2.3.0a allows local users to access sensitive database data. Broadcom identifies PostgreSQL as the affected component but has not published the authentication check, configuration, or credential handling that fails. Access to the SANnav virtual machine and low local privileges are required; successful exploitation exposes database contents to the local user.
The record
- CVE
- CVE-2024-2860
- Published
- May 8, 2024
- Updated
- Aug 1, 2024
- Vendor
- Brocade Communications Systems
- Product
- SANnav
- Classifications
- CWE-306, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 8, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 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
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