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