This page tracks the Alpine Linux fix status. The vulnerability itself is described on the main CVE page. View CVE-2021-32027 →

ALPINE-CVE-2021-32027

Vulnerability in postgresql (ALPINE-CVE-2021-32027)

Summary

Vulnerability in postgresql (ALPINE-CVE-2021-32027). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 11.12-r0 or later.

Original description

The description as published by the source.

A flaw was found in postgresql in versions before 13.3, before 12.7, before 11.12, before 10.17 and before 9.6.22. While modifying certain SQL array values, missing bounds checks let authenticated database users write arbitrary bytes to a wide area of server memory. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.

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 ALPINE-CVE-2021-32027 has been found in postgresql.
Successful exploitation can lead to full system takeover.
What to do: upgrade postgresql to 11.12-r0 or later.
If unsure, ask your IT team or search "postgresql ALPINE-CVE-2021-32027" on the vendor's site.

ALPINE-CVE-2021-32027 (postgresql)
Attack vector: remote (network-reachable) / no user interaction
Patched: 11.12-r0 — 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.

📍 Affected scope

Check the vendor advisory for the affected versions of postgresql.

🔥 Severity

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

🔧 How to fix

Update to 11.12-r0.

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

Affected packages

Alpine:v3.10 postgresql

[{"type":"ECOSYSTEM","events":[{"introduced":"9.6.0"},{"fixed":"11.12-r0"}]}]

Alpine:v3.11 postgresql

[{"type":"ECOSYSTEM","events":[{"introduced":"9.6.0"},{"fixed":"12.7-r0"}]}]

Alpine:v3.12 postgresql

[{"type":"ECOSYSTEM","events":[{"introduced":"9.6.0"},{"fixed":"12.7-r0"}]}]

Alpine:v3.13 postgresql

[{"type":"ECOSYSTEM","events":[{"introduced":"9.6.0"},{"fixed":"13.3-r0"}]}]

Alpine:v3.14 postgresql

[{"type":"ECOSYSTEM","events":[{"introduced":"9.6.0"},{"fixed":"13.3-r0"}]}]

Alpine:v3.15 postgresql13