pgAdmin 4 up to 8.3 pga4_session user session

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.2$0-$5k0.00

Summaryinfo

A vulnerability was found in pgAdmin 4 up to 8.3. It has been classified as problematic. This affects an unknown part. This manipulation of the argument pga4_session causes user session. This vulnerability appears as CVE-2024-2044. The attack may be initiated remotely. In addition, an exploit is available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in pgAdmin 4 up to 8.3. It has been declared as problematic. Affected by this vulnerability is an unknown code block. The manipulation of the argument pga4_session with an unknown input leads to a user session vulnerability. The CWE definition for the vulnerability is CWE-1018. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

pgAdmin 4 uses a file-based session management approach. The session files are saved on disk as pickle objects. When a user performs a request, the value of the session cookie 'pga4_session' is used to retrieve the file, then its content is deserialised, and finally its signature verified. The cookie value is split in 2 parts at the first '!' character. The first part is the session ID (sid), while the second is the session digest. The vulnerability lies in versions of pgAdmin prior to 8.4 where a method loads session files by concatenating the sessions folder - located inside the pgAdmin 4 DATA_DIR - with the session ID. Precisely, the two values are concatenated using the ['os.path.join'] function. It does not set a trusted base-path which should not be escaped

The weakness was presented 03/08/2024 as 7258. The advisory is shared at github.com. This vulnerability is known as CVE-2024-2044 since 02/29/2024. Technical details and also a public exploit are known.

It is possible to download the exploit at 0day.today. It is declared as proof-of-concept.

Upgrading to version 8.4 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at 0day.today (39565). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.4
VulDB Meta Temp Score: 7.2

VulDB Base Score: 5.0
VulDB Temp Score: 4.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 9.9
CNA Vector (PostgreSQL): 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: User session
CWE: CWE-1018
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

0day.today: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: pgAdmin 4 8.4

Timelineinfo

02/29/2024 🔍
03/08/2024 +8 days 🔍
03/08/2024 +0 days 🔍
09/19/2025 +560 days 🔍

Sourcesinfo

Advisory: 7258
Status: Confirmed

CVE: CVE-2024-2044 (🔍)
GCVE (CVE): GCVE-0-2024-2044
GCVE (VulDB): GCVE-100-256093
scip Labs: https://www.scip.ch/en/?labs.20161013

Entryinfo

Created: 03/08/2024 06:45
Updated: 09/19/2025 17:33
Changes: 03/08/2024 06:45 (49), 05/03/2024 11:13 (15), 06/01/2024 09:35 (10), 06/16/2024 09:25 (1), 09/19/2025 17:33 (11)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

 Anonymous User
(+0)
2 years ago
Good morning,
Could you align the cpe with the official one provided by NVD NIST "pgadmin:pgadmin"?
We would appreciate it very much.
Greetings,
TEAM CERT
Thank you, we have just tried to align the CPE.

Want to know what is going to be exploited?

We predict KEV entries!