pgAdmin 4: Connection file paths and parameter keys escape the user's storage directory

Özet

Türkçe özeti henüz hazır değil; şimdilik kaynağın kendi açıklamasını gösteriyoruz.

In server mode pgAdmin 4 resolves a server's password file, SSL certificate, key, CRL and SSH tunnel identity file relative to the user's storage directory, but get_complete_file_path() only stripped leading slashes before joining the two. A path such as "../<another user>/.pgpass", set through the server dialog, the REST API or a servers.json import, therefore named another user's file, and connecting used that user's saved passwords, client certificate or SSH key. The sslkeylogfile connection parameter was passed to libpq unchanged, so a path outside storage let libpq create or append a file as the account running pgAdmin.

make_conninfo() also quoted connection parameter values but not their names, so a crafted parameter name could smuggle additional keyword=value pairs past these checks.

The fix requires the resolved path, with symbolic links followed, to stay inside the user's storage directory or the named shared storage directory, confines sslkeylogfile the same way, and accepts only exact libpq keywords as connection parameter names. A refused path or keyword is reported instead of letting libpq fall back to a default.

This issue affects pgAdmin 4: before 9.19.

Etkilenen sürümler1 yazılım

Kaynaklar4 kaynak

• CVE.org kaydı
• NVD kaydı
• github.com/…ommit/2afe505ef4a31591796449d54ab1604355ff06c2 Yama
• github.com/pgadmin-org/pgadmin4/issues/10650 Üçüncü taraf

Kayıt geçmişi

1. 30 Eki 2026 22:55Yayımlandı

İlgili açıklar

• 6,5 CVE-2026-116252pgAdmin 4: Materialized view refresh redirects its connection through a crafted database name
• 4,2 CVE-2026-116251pgAdmin 4: A user's other sessions survive a change of their password
• 6,5 CVE-2026-116250pgAdmin 4: Files opened in a storage directory follow a symbolic link, hard link or FIFO planted after the containment check
• 6,8 CVE-2026-116248pgAdmin 4: Non-administrators can share a server with every user
• 6,5 CVE-2026-116246pgAdmin 4: Server passwords are left in pgAdmin's process environment
• 8,2 CVE-2026-116247pgAdmin 4: libpq uses the pgAdmin service account's own password file and client certificate