Skip to content

Nokogiri Command Injection Vulnerability

Critical severity GitHub Reviewed Published Aug 19, 2019 to the GitHub Advisory Database • Updated Aug 28, 2023

Package

bundler nokogiri (RubyGems)

Affected versions

< 1.10.4

Patched versions

1.10.4
bundler rexical (RubyGems)
< 1.0.7
1.0.7

Description

A command injection vulnerability in Nokogiri v1.10.3 and earlier allows commands to be executed in a subprocess via Ruby's Kernel.open method. Processes are vulnerable only if the undocumented method Nokogiri::CSS::Tokenizer#load_file is being called with unsafe user input as the filename. This vulnerability appears in code generated by the Rexical gem versions v1.0.6 and earlier. Rexical is used by Nokogiri to generate lexical scanner code for parsing CSS queries. The underlying vulnerability was addressed in Rexical v1.0.7 and Nokogiri upgraded to this version of Rexical in Nokogiri v1.10.4.

References

Published by the National Vulnerability Database Aug 16, 2019
Reviewed Aug 19, 2019
Published to the GitHub Advisory Database Aug 19, 2019
Last updated Aug 28, 2023

Severity

Critical

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
High
Integrity
High
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:H/I:H/A:H

EPSS score

2.018%
(89th percentile)

Weaknesses

CVE ID

CVE-2019-5477

GHSA ID

GHSA-cr5j-953j-xw5p

Source code

Credits

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