Vulnerability in gnupg (UBUNTU-CVE-2018-12020)

Summary

vulnerability in gnupg (UBUNTU-CVE-2018-12020). Data can be tampered with by attackers. Mitigation: upgrade to `1.4.16-1ubuntu2.5` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **UBUNTU-CVE-2018-12020** has been found in gnupg. Data can be tampered with by attackers. CVSS score: ?/10. What to do: upgrade gnupg to **1.4.16-1ubuntu2.5** or later. If unsure, ask your IT team or search "gnupg UBUNTU-CVE-2018-12020" on the vendor's site.

UBUNTU-CVE-2018-12020 (gnupg) — Attack vector: remote (network-reachable) / unauthenticated / no user interaction Patched: `1.4.16-1ubuntu2.5` — 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 gnupg.

📍 Affected scope

gnupg — .

🔥 Severity

Severity: ?. Data can be tampered with by attackers

🔧 How to fix

Update to **1.4.16-1ubuntu2.5**.

🛡️ 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 'gnupg' .` 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

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

Affected packages

Ubuntu:14.04:LTS gnupg

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.4.16-1ubuntu2.5"}]}]

Ubuntu:14.04:LTS gnupg2

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.22-3ubuntu1.4"}]}]

Ubuntu:Pro:14.04:LTS python-gnupg

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.3.6-1ubuntu0.1~esm1"}]}]

Ubuntu:16.04:LTS gnupg

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.4.20-1ubuntu3.2"}]}]

Ubuntu:16.04:LTS gnupg2

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.1.11-6ubuntu2.1"}]}]

Ubuntu:Pro:16.04:LTS python-gnupg

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.3.8-2ubuntu0.1~esm1"}]}]

Ubuntu:16.04:LTS enigmail