← Back
USN-8018-2
Vulnerability in python3.4 (USN-8018-2)
Summary
vulnerability in python3.4 (USN-8018-2). Risk of unauthorized operations or information disclosure. Exploitable via `Cookie header`. Mitigation: upgrade to `3.4.3-1ubuntu1~14.04.7+esm20` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **USN-8018-2** has been found in python3.4.
Attackers can target a specific entry point like `Cookie header` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade python3.4 to **3.4.3-1ubuntu1~14.04.7+esm20** or later.
If unsure, ask your IT team or search "python3.4 USN-8018-2" on the vendor's site.
USN-8018-2 (python3.4) —
Attack surface: Cookie header
Patched: `3.4.3-1ubuntu1~14.04.7+esm20` — 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 python3.4. Attackers reach the vulnerable code path via `Cookie header` without authentication.
📍 Affected scope
python3.4 — . Attack surface: Cookie header.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **3.4.3-1ubuntu1~14.04.7+esm20**.
🛡️ 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 'python3.4' .` 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 'python3.4' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `python3.4` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade python3.4 to 3.4.3-1ubuntu1~14.04.7+esm20ステージング環境で 3.4.3-1ubuntu1~14.04.7+esm20 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Ubuntu:Pro:14.04:LTS
python3.4
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.4.3-1ubuntu1~14.04.7+esm20"}]}]
Ubuntu:Pro:14.04:LTS
python3.5
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.5.2-2ubuntu0~16.04.4~14.04.1+esm10"}]}]
Ubuntu:Pro:16.04:LTS
python3.5
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.5.2-2ubuntu0~16.04.13+esm22"}]}]
Ubuntu:Pro:18.04:LTS
python3.6
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.6.9-1~18.04ubuntu1.13+esm9"}]}]
Ubuntu:Pro:18.04:LTS
python3.7
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.7.5-2ubuntu1~18.04.2+esm10"}]}]
Ubuntu:Pro:18.04:LTS
python3.8
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.8.0-3ubuntu1~18.04.2+esm10"}]}]
Ubuntu:Pro:20.04:LTS
python3.8
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.8.10-0ubuntu1~20.04.18+esm6"}]}]
Ubuntu:Pro:20.04:LTS
python3.9
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.9.5-3ubuntu0~20.04.1+esm10"}]}]
Ubuntu:22.04:LTS
python3.10
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.12-1~22.04.15"}]}]
Ubuntu:Pro:22.04:LTS
python3.11
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.11.0~rc1-1~22.04.1~esm9"}]}]
Ubuntu:24.04:LTS
python3.12
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.12.3-1ubuntu0.12"}]}]
Ubuntu:25.10
python3.13
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.13.7-1ubuntu0.4"}]}]
Ubuntu:25.10
python3.14
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.14.0-1ubuntu0.3"}]}]