← Back
ROOT-APP-MAVEN-CVE-2023-26119

Vulnerability in io.root.net.sourceforge.htmlunit:htmlunit (ROOT-APP-MAVEN-CVE-2023-26119)

Summary

vulnerability in io.root.net.sourceforge.htmlunit:htmlunit (ROOT-APP-MAVEN-CVE-2023-26119). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `2.70.0-root.io.1, 2.70.0-root.io.2` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **ROOT-APP-MAVEN-CVE-2023-26119** has been found in io.root.net.sourceforge.htmlunit:htmlunit. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade io.root.net.sourceforge.htmlunit:htmlunit to **2.70.0-root.io.1, 2.70.0-root.io.2** or later. If unsure, ask your IT team or search "io.root.net.sourceforge.htmlunit:htmlunit ROOT-APP-MAVEN-CVE-2023-26119" on the vendor's site.
ROOT-APP-MAVEN-CVE-2023-26119 (io.root.net.sourceforge.htmlunit:htmlunit) — Patched: `2.70.0-root.io.1, 2.70.0-root.io.2` — 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 io.root.net.sourceforge.htmlunit:htmlunit.
📍 Affected scope
io.root.net.sourceforge.htmlunit:htmlunit — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.70.0-root.io.1, 2.70.0-root.io.2**.
🛡️ 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 'io.root.net.sourceforge.htmlunit:htmlunit' .` 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. 1
    Identify exposure identify
    grep -r 'io.root.net.sourceforge.htmlunit:htmlunit' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `io.root.net.sourceforge.htmlunit:htmlunit` を grep し、稼働しているサービス・バージョンを把握する。

  2. 6
    Apply patch patch
    Upgrade io.root.net.sourceforge.htmlunit:htmlunit to 2.70.0-root.io.1, 2.70.0-root.io.2

    ステージング環境で 2.70.0-root.io.1, 2.70.0-root.io.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  3. 7
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

Root:Maven io.root.net.sourceforge.htmlunit:htmlunit
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.70.0-root.io.1"},{"fixed":"2.70.0-root.io.2"}]}]
Root:Maven net.sourceforge.htmlunit:htmlunit
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.70.0-aikido.2"}]}]

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →