Pgadmin: Exposure of Data Element to Wrong Session
CVE-2023-1907 is a high-severity exposure of data element to wrong session vulnerability in Pgadmin, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists version 7.0 as the first without the flaw, so updating Pgadmin to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.45% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Pgadmin to 7.0 or a later version.
Affected products and versions
Version data comes from NVD's product matching. 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
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- LowA basic user account is enough.
- 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:H/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.0 | High | CNA (redhat.com) |
| CVSS 3.1 | 7.5 | High | NVD |
| CVSS 3.1 | 8.0 | High | CISA (ADP) |
Official description
A vulnerability was found in pgadmin. Users logging into pgAdmin running in server mode using LDAP authentication may be attached to another user's session if multiple connection attempts occur simultaneously.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Exposure of Data Element to Wrong Session
The product does not sufficiently enforce boundaries between the states of different sessions, causing data to be provided to, or used by, the wrong session.
How developers prevent this class of flaw
- Protect the application's sessions from information leakage. Make sure that a session's data is not used or visible by other sessions.
- Use a static analysis tool to scan the code for information leakage vulnerabilities (e.g. Singleton Member Field).
- In a multithreading environment, storing user data in Servlet member fields introduces a data access race condition. Do not use member fields to store information in the Servlet.
More Exposure of Data Element to Wrong Session vulnerabilities (CWE-488)
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
- access.redhat.com/security/cve/CVE-2023-1907Third Party Advisory
- bugzilla.redhat.com/show_bug.cgi?id=2218384Issue Tracking, Third Party Advisory
Other vulnerabilities in Pgadmin
- 8.8 High severity
Recent Exposure of Data Element to Wrong Session vulnerabilities
- 7.5 High severity
- 8.0 High severity
- 9.6 Critical severity
- 7.5 High severity
- 8.3 High severity
- 9.1 Critical severity
Spotted an error? Tell us.