To pass a server's password to psql and to the utilities pgAdmin 4 runs as background processes, the server manager wrote it into pgAdmin's own…
To pass a server's password to psql and to the utilities pgAdmin 4 runs as background processes, the server manager wrote it into pgAdmin's own process environment: as PGPASSWORD for the PSQL tool, and under a per-process variable for a utility. Nothing removed it afterwards. pgAdmin's environment is shared by every user's requests and copied into every process it starts, so in server mode another user's later PSQL session or utility inherited the password, and libpq used PGPASSWORD for any connection made without a password of its own, letting one user connect with another user's saved password. The fix puts the password only into the environment built for the process that needs it and star
Read at NIST National Vulnerability Database (CVE API 2.0)
- Vendor
- Pgadmin.Org
- Product
- pgAdmin 4
- CVSS v3.1
- 6.5 AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:L/A:N
- Weakness
- CWE-214, CWE-526
- NVD status
- Received
Why it ranks 9 (Routine)
- CVSS v3.1 6.5 medium
- Recency: items published within 24 hours gain 15, within 72 hours 6, within 7 days 2.