Skip to content

pgAdmin 4 Path Traversal vulnerability

Moderate severity GitHub Reviewed Published Mar 17, 2022 to the GitHub Advisory Database • Updated Jun 30, 2023

Package

pip pgadmin4 (pip)

Affected versions

< 6.7

Patched versions

6.7

Description

When run in server mode, pgAdmin 4 allows users to store files on the server under individual storage directories. Files such as SQL scripts may be uploaded through the user interface. The URI to which upload requests are made fails to validate the upload path to prevent path traversal techniques being used to store files outside of the storage directory. A malicious, but authorised and authenticated user can construct an HTTP request using their existing CSRF token and session cookie to manually upload files to any location that the operating system user account under which pgAdmin is running has permission to write.

References

Published by the National Vulnerability Database Mar 16, 2022
Published to the GitHub Advisory Database Mar 17, 2022
Reviewed Jun 30, 2023
Last updated Jun 30, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

EPSS score

0.063%
(28th percentile)

Weaknesses

CVE ID

CVE-2022-0959

GHSA ID

GHSA-cr8c-972v-rmp3

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.