Cross-account session exposure via concurrent LDAP logins
Published Jan 9, 2025 · Updated Aug 27, 2025
Session isolation failure in pgAdmin 4 before 7.0 allows remote authenticated users to enter another user's session during concurrent LDAP logins. The login handler processed simultaneous authentication workflows without a mutex, allowing session state to become associated with the wrong user. Server mode with LDAP enabled and another user logging in at the same time are required; the mix-up exposes that user's pgAdmin access and data.
Summary
What happened
Session isolation failure in pgAdmin 4 before 7.0 allows remote authenticated users to enter another user's session during concurrent LDAP logins. The login handler processed simultaneous authentication workflows without a mutex, allowing session state to become associated with the wrong user. Server mode with LDAP enabled and another user logging in at the same time are required; the mix-up exposes that user's pgAdmin access and data.
The record
- CVE
- CVE-2023-1907
- Published
- Jan 9, 2025
- Updated
- Aug 27, 2025
- Vendor
- pgAdmin Development Team
- Product
- pgAdmin 4
- Classifications
- CWE-488, CWE-276, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 9, 2025CVE publishedPublication date reported by the CVE source.
- Aug 27, 2025Record 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 <7.0
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