Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2022-40674 high CVSS 8.1

Use-After-Free in libexpat (CVE-2022-40674)

Summary

Vulnerability in libexpat (CVE-2022-40674). Successful exploitation can lead to full system takeover.

Original description

The description as published by the source.

libexpat before 2.4.9 has a use-after-free in the doContent function in xmlparse.c.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

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 weakness called CVE-2022-40674 was discovered in libexpat.
In plain terms, it is a use-after-free flaw that often leads to attacker takeover.
Severity is High (CVSS 8.1/10). If exploited, attackers can leak data or disrupt key functionality.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "libexpat CVE-2022-40674".

CVE-2022-40674 (libexpat). Severity: High / CVSSv3 8.1. Category: CWE-416.
Response plan:

  1. Check the vendor advisory for affected versions and the patched release.
  2. If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
  3. If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
  4. Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
    PoCs and fix commits: see the 'References' section, MITRE, and NVD.
❓ What is the problem

A weakness (CVE-2022-40674) in libexpat. In plain words, it is a use-after-free flaw that often leads to attacker takeover.

📍 Affected scope

Target versions of libexpat (see vendor advisory). If running in production, identify exposure immediately.

🔥 Severity

Severity: High (CVSS 8.1/10). If exploited, attackers can leak data or disrupt key functionality.

🔧 How to fix

Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-416)

🛡️ Workaround

If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.

🔍 Detection

Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

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