When a server in pgAdmin 4 had no password file, client certificate or client key configured, or the configured one could not be found, pgAdmin left…
When a server in pgAdmin 4 had no password file, client certificate or client key configured, or the configured one could not be found, pgAdmin left the parameter out of the connection and libpq fell back to the defaults of the operating-system account running pgAdmin: ~/.pgpass, ~/.postgresql/postgresql.crt and postgresql.key, or PGPASSFILE, PGSSLCERT and PGSSLKEY. In server mode any user could therefore connect to a server with the service account's saved passwords or client certificate, and supplying only a copy of its public certificate was enough for libpq to pair it with the service account's private key. A pg_service.conf entry, or a maintenance database name read as a connection stri
Read at NIST National Vulnerability Database (CVE API 2.0)
- Vendor
- Pgadmin.Org
- Product
- pgAdmin 4
- CVSS v3.1
- 8.2 AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N
- Weakness
- CWE-522, CWE-1188
- Exposure class
- Database
- NVD status
- Received
Why it ranks 21 (Routine)
- CVSS v3.1 8.2 high
- Product class: database
- Recency: items published within 24 hours gain 15, within 72 hours 6, within 7 days 2.