CVE-2024-2044
Pgadmin 4 ≤ 8.4
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2024-2044 is a critical-severity Path Traversal: 'dir\..\..\filename' (CWE-31) vulnerability in Pgadmin Pgadmin 4. Its CVSS base score is 9.9 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 0.4% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and AC-3 (Access Enforcement) — 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.3 and earlier are affected by a path-traversal flaw in the session-handling code that deserializes user sessions. The vulnerability stems from unsafe handling of pickle objects and is tracked under CWE-31, carrying a CVSS 3.1 score of 9.9.
On Windows, an unauthenticated remote attacker can supply a crafted path to load and deserialize arbitrary pickle objects, resulting in code execution. On POSIX or Linux systems the same outcome requires an authenticated attacker who can first upload a malicious pickle file before triggering deserialization.
Public references including the pgadmin-org GitHub issue 7258, a Shielder advisory, and Fedora package-announce lists document the issue and link to subsequent updates. The associated EPSS score stands at 0.8347 with no indicated rise from a lower baseline.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-1004
Vulnerability Data
pgAdmin <= 8.3 is affected by a path-traversal vulnerability while deserializing users’ sessions in the session handling code. If the server is running on Windows, an unauthenticated attacker can load and deserialize remote pickle objects and gain code execution. If…
more
the server is running on POSIX/Linux, an authenticated attacker can upload pickle objects, deserialize them, and gain code execution.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Directly requires validation of path inputs, stopping the acceptance of backslash dot-dot sequences that escape the restricted directory.
Enforces authorization checks on file/resource access, blocking exploitation of a traversed path even if the malformed name is accepted.
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.
Secure SDLC practices directly require input validation and path sanitization that block this weakness.
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.
Security testing can discover traversal flaws but does not prevent them at the source.
Secure development lifecycle mandates input validation and path sanitization that directly blocks directory traversal sequences.
Application security requirements explicitly call for controls against path traversal and other injection flaws.
Secure architecture principles reduce the attack surface but do not prescribe the specific coding fix.
Secure coding standards require canonicalization and whitelist validation that eliminate CWE-31.