Vulnerability in postgresql-9.3 (UBUNTU-CVE-2025-8714)

Summary

Vulnerability in postgresql-9.3 (UBUNTU-CVE-2025-8714). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 14.19-0ubuntu0.22.04.1 or later.

Original description

The description as published by the source.

Untrusted data inclusion in pg_dump in PostgreSQL allows a malicious superuser of the origin server to inject arbitrary code for restore-time execution as the client operating system account running psql to restore the dump, via psql meta-commands. pg_dumpall is also affected. pg_restore is affected when used to generate a plain-format dump. This is similar to MySQL CVE-2024-21096. Versions before PostgreSQL 17.6, 16.10, 15.14, 14.19, and 13.22 are affected.

Source: OSV.dev (Open Source Vulnerabilities) OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as UBUNTU-CVE-2025-8714 has been found in postgresql-9.3.
Successful exploitation can lead to full system takeover.
What to do: upgrade postgresql-9.3 to 14.19-0ubuntu0.22.04.1 or later.
If unsure, ask your IT team or search "postgresql-9.3 UBUNTU-CVE-2025-8714" on the vendor's site.

UBUNTU-CVE-2025-8714 (postgresql-9.3)
Attack vector: remote (network-reachable) / unauthenticated
Patched: 14.19-0ubuntu0.22.04.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in postgresql-9.3.

📍 Affected scope

Check the vendor advisory for the affected versions of postgresql-9.3.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 14.19-0ubuntu0.22.04.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'postgresql-9.3' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'postgresql-9.3' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で postgresql-9.3 を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade postgresql-9.3 to 14.19-0ubuntu0.22.04.1
```
ステージング環境で 14.19-0ubuntu0.22.04.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Ubuntu:Pro:14.04:LTS postgresql-9.3

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Ubuntu:Pro:16.04:LTS postgresql-9.5

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Ubuntu:Pro:18.04:LTS postgresql-10

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Ubuntu:20.04:LTS postgresql-12

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Ubuntu:22.04:LTS postgresql-14

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.19-0ubuntu0.22.04.1"}]}]

Ubuntu:24.04:LTS postgresql-16

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.10-0ubuntu0.24.04.1"}]}]

Ubuntu:25.10 postgresql-17

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.6-1"}]}]

References

advisory ubuntu.com
advisory ubuntu.com
report ubuntu.com
report cve.org
report postgresql.org
report postgresql.org