Vulnerability in libxmljs (CVE-2022-21144)
Summary
Vulnerability in libxmljs (CVE-2022-21144). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.19.8 or later.
Original description
The description as published by the source.
libxmljs provides libxml bindings for v8 javascript engine. This affects all versions of package libxmljs. When invoking the libxmljs.parseXml function with a non-buffer argument the V8 code will attempt invoking the .toString method of the argument. If the argument's toString value is not a Function object V8 will crash.
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-21144 has been found in libxmljs.
Risk of unauthorized operations or information disclosure.
What to do: upgrade libxmljs to 0.19.8 or later.
If unsure, ask your IT team or search "libxmljs CVE-2022-21144" on the vendor's site.
CVE-2022-21144 (libxmljs) — CWE-20
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.19.8 — 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.
A vulnerability (CWE-20) exists in libxmljs.
Check the vendor advisory for the affected versions of libxmljs.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.19.8.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'libxmljs' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'libxmljs' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
libxmljsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade libxmljs to 0.19.8ステージング環境で 0.19.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web snyk.io