← Back
USN-8072-1
Vulnerability in postgresql-14 (USN-8072-1)
Summary
vulnerability in postgresql-14 (USN-8072-1). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `14.22-0ubuntu0.22.04.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **USN-8072-1** has been found in postgresql-14.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade postgresql-14 to **14.22-0ubuntu0.22.04.1** or later.
If unsure, ask your IT team or search "postgresql-14 USN-8072-1" on the vendor's site.
USN-8072-1 (postgresql-14) —
Patched: `14.22-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-14.
📍 Affected scope
postgresql-14 — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **14.22-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-14' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'postgresql-14' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `postgresql-14` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade postgresql-14 to 14.22-0ubuntu0.22.04.1ステージング環境で 14.22-0ubuntu0.22.04.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Ubuntu:22.04:LTS
postgresql-14
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.22-0ubuntu0.22.04.1"}]}]
Ubuntu:24.04:LTS
postgresql-16
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.13-0ubuntu0.24.04.1"}]}]
Ubuntu:25.10
postgresql-17
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.9-0ubuntu0.25.10.1"}]}]