← Back
UBUNTU-CVE-2022-21340
Vulnerability in openjdk-8 (UBUNTU-CVE-2022-21340)
Summary
vulnerability in openjdk-8 (UBUNTU-CVE-2022-21340). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `8u342-b07-0ubuntu1~16.04` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **UBUNTU-CVE-2022-21340** has been found in openjdk-8.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade openjdk-8 to **8u342-b07-0ubuntu1~16.04** or later.
If unsure, ask your IT team or search "openjdk-8 UBUNTU-CVE-2022-21340" on the vendor's site.
UBUNTU-CVE-2022-21340 (openjdk-8) —
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `8u342-b07-0ubuntu1~16.04` — 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 openjdk-8.
📍 Affected scope
openjdk-8 — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **8u342-b07-0ubuntu1~16.04**.
🛡️ 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 'openjdk-8' .` 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 'openjdk-8' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `openjdk-8` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade openjdk-8 to 8u342-b07-0ubuntu1~16.04ステージング環境で 8u342-b07-0ubuntu1~16.04 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Ubuntu:Pro:16.04:LTS
openjdk-8
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8u342-b07-0ubuntu1~16.04"}]}]
Ubuntu:16.04:LTS
icedtea-web
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:16.04:LTS
openjdk-9
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:18.04:LTS
openjdk-17
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.0.2+8-1~18.04"}]}]
Ubuntu:18.04:LTS
openjdk-8
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8u342-b07-0ubuntu1~18.04"}]}]
Ubuntu:18.04:LTS
openjdk-lts
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"11.0.14+9-0ubuntu2~18.04"}]}]
Ubuntu:18.04:LTS
icedtea-web
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:20.04:LTS
openjdk-17
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.0.2+8-1~20.04"}]}]
Ubuntu:20.04:LTS
openjdk-8
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8u342-b07-0ubuntu1~20.04"}]}]
Ubuntu:20.04:LTS
openjdk-lts
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"11.0.14+9-0ubuntu2~20.04"}]}]
Ubuntu:20.04:LTS
icedtea-web
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:20.04:LTS
openjdk-13
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:20.04:LTS
openjdk-16
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:22.04:LTS
icedtea-web
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:22.04:LTS
openjdk-18
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:22.04:LTS
openjdk-8
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8u342-b07-0ubuntu1~22.04"}]}]
Ubuntu:24.04:LTS
icedtea-web
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:25.10
icedtea-web
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:26.04:LTS
icedtea-web
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]