CVE-2024-2044

Pgadmin 4 insecure deserialization

9.9 CRITICALPublic exploitEPSS 79.5%

Published7 Mar 2024

Description

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 the server is running on POSIX/Linux, an authenticated attacker can upload pickle objects, deserialize them, and gain code execution.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredLow

User interactionNone

ScopeChanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Affected products

Pgadmin 4< 8.4

Fedoraproject Fedora40

Remediation

Fixed in

Pgadmin 4≥ 8.4

Patch & vendor advisories

https://github.com/pgadmin-org/pgadmin4/issues/7258

References

https://github.com/pgadmin-org/pgadmin4/issues/7258Issue TrackingVendor Advisory
https://lists.fedoraproject.org/archives/list/[email protected]/message/LUYN2JXKKHFSVTASH344TBRGWDH64XQV/Mailing List
https://www.shielder.com/advisories/pgadmin-path-traversal_leads_to_unsafe_deserialization_and_rce/ExploitThird Party Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2024-2044 being actively exploited?

CVE-2024-2044 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 79.5%.

How severe is CVE-2024-2044?

CVE-2024-2044 has a CVSS 3.1 base score of 9.9, rated critical. EPSS estimates a 79.5% probability of exploitation.

Which products are affected by CVE-2024-2044?

Affected products include Pgadmin 4, Fedoraproject Fedora.

How do I fix CVE-2024-2044?

Upgrade affected software to a fixed version, for example Pgadmin 4 8.4 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-2044 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.