CVE-2024-9014
Exposed Creds in Pgadmin 4 ≤ 8.12
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2024-9014 is a critical-severity Insufficiently Protected Credentials (CWE-522) vulnerability in Pgadmin Pgadmin 4. Its CVSS base score is 9.9 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Unsecured Credentials (T1552); ranked in the top 5% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SC-28 (Protection of Information at Rest) and SC-8 (Transmission Confidentiality and Integrity) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
pgAdmin versions 8.11 and earlier contain a flaw in their OAuth2 authentication implementation that can expose the client ID and secret. The affected component is the pgAdmin web application, which uses these credentials to integrate with external identity providers. The vulnerability is tracked as CWE-522 and carries a CVSS 3.1 score of 9.9.
An authenticated remote attacker can retrieve the OAuth2 client credentials and leverage them to obtain unauthorized access to user data. Because the attack requires only low-privilege credentials and no user interaction, an adversary with a valid pgAdmin account can escalate to full confidentiality, integrity, and availability impact across the application scope.
The single reference points to a GitHub issue opened by the pgAdmin project; no advisory text or patch details are supplied in the available inputs. The EPSS score sits at 0.9288 with no material rise from a lower baseline.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-2825
Vulnerability Data
pgAdmin versions 8.11 and earlier are vulnerable to a security flaw in OAuth2 authentication. This vulnerability allows an attacker to potentially obtain the client ID and secret, leading to unauthorized access to user data.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 1 hardening rule · 1 OS baseline
V11.3.3
Mitigating Controls (NIST 800-53 r5) AI
Protection of information at rest requires encryption or equivalent safeguards for stored credentials.
Transmission confidentiality and integrity enforcement stops credentials from being sent in plaintext or without protection.
Authenticator management requires secure generation, storage, and distribution of credentials, directly stopping insecure methods.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Encrypting data-at-rest fully prevents insecure credential storage while only partially satisfying the broader data-protection outcome.
Encrypting data-in-transit fully prevents interception of credentials in motion while only partially satisfying the broader data-protection outcome.
Credential management practices directly reduce insecure storage/transmission but do not guarantee encryption or transport protection.
Protecting identity assertions covers conveyance of credentials but is narrower than full credential lifecycle protection.
Authentication policies can enforce stronger credential handling yet address only verification, not storage or transit protection.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Requiring protected storage, transmission, and non-display of passwords prevents credentials from being stored or sent in clear text where they can be harvested by unauthorized actors.
Protecting secret and private keys against disclosure and unauthorized use decreases the exposure of credentials that are stored or transmitted in recoverable form.
Forbidding clear-text transmission and display of passwords, plus the use of stronger alternatives to passwords, prevents credentials from being obtained or reused by attackers.
Acceptable-use expectations that cover protection of credentials and information assets throughout their lifecycle discourage practices that expose or mishandle authentication material.
Contractual clauses that survive termination help ensure that credentials and other secrets are not retained or misused after employment ends.
Regular reminders about password security and personal accountability make users less likely to store or transmit credentials in cleartext or other unprotected forms.