Categories
CVE-2022-29546

Vulnerability in net.sourceforge.htmlunit:neko-htmlunit (CVE-2022-29546)

Summary

Vulnerability in net.sourceforge.htmlunit:neko-htmlunit (CVE-2022-29546). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.61.0 or later.

Original description

The description as published by the source.

HtmlUnit NekoHtml Parser before 2.61.0 suffers from a denial of service vulnerability. Crafted input associated with the parsing of Processing Instruction (PI) data leads to heap memory consumption. This is similar to CVE-2022-28366 but affects a much later version of the product.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2022-29546 has been found in net.sourceforge.htmlunit:neko-htmlunit.
Risk of unauthorized operations or information disclosure.
What to do: upgrade net.sourceforge.htmlunit:neko-htmlunit to 2.61.0 or later.
If unsure, ask your IT team or search "net.sourceforge.htmlunit:neko-htmlunit CVE-2022-29546" on the vendor's site.

CVE-2022-29546 (net.sourceforge.htmlunit:neko-htmlunit) — CWE-400
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.61.0 — 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 (CWE-400) exists in net.sourceforge.htmlunit:neko-htmlunit.

📍 Affected scope

Check the vendor advisory for the affected versions of net.sourceforge.htmlunit:neko-htmlunit.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.61.0.

🛡️ 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. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで net.sourceforge.htmlunit:neko-htmlunit を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch
    Upgrade net.sourceforge.htmlunit:neko-htmlunit to 2.61.0

    ステージング環境で 2.61.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

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

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

Affected packages

Maven net.sourceforge.htmlunit:neko-htmlunit
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.61.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details