Skip to content

Nokogiri Improperly Handles Unexpected Data Type

High severity GitHub Reviewed Published May 8, 2022 in sparklemotion/nokogiri • Updated May 4, 2023

Package

bundler nokogiri (RubyGems)

Affected versions

< 1.13.6

Patched versions

1.13.6

Description

Summary

Nokogiri < v1.13.6 does not type-check all inputs into the XML and HTML4 SAX parsers. For CRuby users, this may allow specially crafted untrusted inputs to cause illegal memory access errors (segfault) or reads from unrelated memory.

Severity

The Nokogiri maintainers have evaluated this as High 8.2 (CVSS3.1).

Mitigation

CRuby users should upgrade to Nokogiri >= 1.13.6.

JRuby users are not affected.

Workarounds

To avoid this vulnerability in affected applications, ensure the untrusted input is a String by calling #to_s or equivalent.

Credit

This vulnerability was responsibly reported by @agustingianni and the Github Security Lab.

References

@flavorjones flavorjones published to sparklemotion/nokogiri May 8, 2022
Published by the National Vulnerability Database May 20, 2022
Published to the GitHub Advisory Database May 23, 2022
Reviewed May 23, 2022
Last updated May 4, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H

EPSS score

0.284%
(68th percentile)

Weaknesses

CVE ID

CVE-2022-29181

GHSA ID

GHSA-xh29-r2w5-wx8m

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.