High [CVE-2022-50998] Denial of Service and Memory Corruption via Crafted XML Input
This high-severity Red Hat Linux advisory covers CVE-2022-50998 affecting Red Hat 3scale API Management Platform 2, Red Hat Satellite 6.
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
Nokogiri before 1.13.9 (CRuby implementation using packaged libraries) bundles libxml2 v2.9.14, which is affected by CVE-2022-40304 (data corruption / double-free from an entity reference cycle when entity content is allocated from a dict) and CVE-2022-40303 (integer overflows when parsing with XML_PARSE_HUGE).
Nokogiri 1.13.9 upgrades the packaged libxml2 to v2.10.3 to address these issues.
Processing crafted XML input may lead to denial of service or memory corruption. (The advisory also references CVE-2022-2309, a NULL pointer dereference via iterwalk/canonicalize, which maintainers determined does not affect Nokogiri users.) A flaw was found in Nokogiri, a Ruby gem for parsing XML and HTML documents.
This vulnerability arises from issues within its bundled libxml2 library, specifically involving data corruption from entity reference cycles and integer overflows when processing large XML files.
A remote attacker could exploit these flaws by providing specially crafted XML input, potentially leading to denial of service or memory corruption within the application. Red Hat severity: Important — CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).
Weakness: CWE-190. Affected Red Hat products: Red Hat 3scale API Management Platform 2; Red Hat Satellite 6.
Red Hat does not currently list a fixing RHSA for this CVE.
- < 1.13.9
- < 9.14
Official advisory · high-confidence parse· fetched 46 minutes ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 46 minutes ago·verify at source
Mitigation
The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.
Official advisory · high-confidence parse· fetched 46 minutes ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.