← Back
CVE-2022-21476
Vulnerability in java (CVE-2022-21476)
Summary
vulnerability in java (CVE-2022-21476). Confidential information can be exposed externally. Mitigation: upgrade to `1.7.0, 1.8.0, 7.0.341, 8.0.331, 11.0.15, 17.0.3, 18.0.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2022-21476** has been found in java.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade java to **1.7.0, 1.8.0, 7.0.341, 8.0.331, 11.0.15, 17.0.3, 18.0.1** or later.
If unsure, ask your IT team or search "java CVE-2022-21476" on the vendor's site.
CVE-2022-21476 (java) —
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `1.7.0, 1.8.0, 7.0.341, 8.0.331, 11.0.15, 17.0.3, 18.0.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 java.
📍 Affected scope
java — .
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **1.7.0, 1.8.0, 7.0.341, 8.0.331, 11.0.15, 17.0.3, 18.0.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 'java' .` 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 'java' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `java` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade java to 1.7.0, 1.8.0, 7.0.341, 8.0.331, 11.0.15, 17.0.3, 18.0.1ステージング環境で 1.7.0, 1.8.0, 7.0.341, 8.0.331, 11.0.15, 17.0.3, 18.0.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Bitnami
java
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.7.0"},{"introduced":"1.8.0"},{"fixed":"1.8.0"},{"introduced":"7.0.0"},{"fixed":"7.0.341"},{"introduced":"8.0.0"},{"fixed":"8.0.331"},{"introduced":"9.0.0"},{"fixed":"11.0.15"},{"introduced":"12.0.0"},{"fixed":"17.0.3"},{"introduced":"18.0.0"},{"fixed":"18.0.1"}]}]
Bitnami
java-min
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.7.0"},{"introduced":"1.8.0"},{"fixed":"1.8.0"},{"introduced":"7.0.0"},{"fixed":"7.0.341"},{"introduced":"8.0.0"},{"fixed":"8.0.331"},{"introduced":"9.0.0"},{"fixed":"11.0.15"},{"introduced":"12.0.0"},{"fixed":"17.0.3"},{"introduced":"18.0.0"},{"fixed":"18.0.1"}]}]
Bitnami
jre
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.7.0"},{"introduced":"1.8.0"},{"fixed":"1.8.0"},{"introduced":"7.0.0"},{"fixed":"7.0.341"},{"introduced":"8.0.0"},{"fixed":"8.0.331"},{"introduced":"9.0.0"},{"fixed":"11.0.15"},{"introduced":"12.0.0"},{"fixed":"17.0.3"},{"introduced":"18.0.0"},{"fixed":"18.0.1"}]}]
References
- advisory https://lists.debian.org/debian-lts-announce/2022/05/msg00017.html
- advisory https://security.netapp.com/advisory/ntap-20220429-0006/
- advisory https://www.debian.org/security/2022/dsa-5128
- advisory https://www.debian.org/security/2022/dsa-5131
- patch https://www.oracle.com/security-alerts/cpuapr2022.html
- web https://nvd.nist.gov/vuln/detail/CVE-2022-21476