Authenticated arbitrary file write via unnormalized upload path
Published Mar 16, 2022 · Updated Aug 2, 2024
Path traversal in pgAdmin 4 before 6.7 allows remote authenticated users to write files outside their server storage directories. The file manager upload handler checked an unnormalized request path with pathlib.Path.relative_to, allowing traversal components to escape the per-user directory. The flaw requires server mode, a valid session cookie, and a CSRF token; writes remain limited to locations accessible to the pgAdmin OS account.
Summary
What happened
Path traversal in pgAdmin 4 before 6.7 allows remote authenticated users to write files outside their server storage directories. The file manager upload handler checked an unnormalized request path with pathlib.Path.relative_to, allowing traversal components to escape the per-user directory. The flaw requires server mode, a valid session cookie, and a CSRF token; writes remain limited to locations accessible to the pgAdmin OS account.
The record
- CVE
- CVE-2022-0959
- Published
- Mar 16, 2022
- Updated
- Aug 2, 2024
- Vendor
- pgAdmin Development Team
- Product
- pgAdmin 4
- Classifications
- CWE-22, CWE-434, T1105
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 16, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=pgadmin 6.7
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo