Impact
An incomplete path traversal fix in pghoard versions up to and including v2.7.1 allows an attacker with write access to the backup object storage (such as S3, GCS, or Azure) to execute arbitrary file writes and directory creation outside the designated PostgreSQL data directory (pgdata).
When a database administrator executes a restore operation (via pghoard_restore get-basebackup), a maliciously crafted delta backup manifest with path traversal sequences (e.g., ../../../../etc/cron.d/backdoor) will write arbitrary payloads to the host system.
Patches
The problem will be patched in version 2.7.2. Users should upgrade to 2.7.2 as soon as it is released.
Workarounds
There are no known workarounds. Please apply a patch or upgrade.
Credits
This vulnerability has been reported through our bug bounty program, by Dennis Sepede
Impact
An incomplete path traversal fix in
pghoardversions up to and includingv2.7.1allows an attacker with write access to the backup object storage (such as S3, GCS, or Azure) to execute arbitrary file writes and directory creation outside the designated PostgreSQL data directory (pgdata).When a database administrator executes a restore operation (via
pghoard_restore get-basebackup), a maliciously crafted delta backup manifest with path traversal sequences (e.g.,../../../../etc/cron.d/backdoor) will write arbitrary payloads to the host system.Patches
The problem will be patched in version
2.7.2. Users should upgrade to2.7.2as soon as it is released.Workarounds
There are no known workarounds. Please apply a patch or upgrade.
Credits
This vulnerability has been reported through our bug bounty program, by Dennis Sepede