Nokogiri up to 1.10.3 Ruby Tokenizer#load_file Filename command injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.1 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in Nokogiri up to 1.10.3. The impacted element is the function Nokogiri::CSS::Tokenizer#load_file of the component Ruby. The manipulation as part of Filename results in command injection.
This vulnerability was named CVE-2019-5477. The attack may be performed from remote. There is no available exploit.
You should upgrade the affected component.
Details
A vulnerability, which was classified as critical, was found in Nokogiri up to 1.10.3. Affected is the function Nokogiri::CSS::Tokenizer#load_file of the component Ruby. The manipulation as part of a Filename leads to a command injection vulnerability. CWE is classifying the issue as CWE-77. The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
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.
The weakness was presented 08/16/2019 (GitHub Repository). The advisory is shared for download at github.com. This vulnerability is traded as CVE-2019-5477 since 01/04/2019. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1202.
Upgrading to version 1.10.4 eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.1
VulDB Base Score: 7.3
VulDB Temp Score: 6.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Command injectionCWE: CWE-77 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Nokogiri 1.10.4
Timeline
01/04/2019 🔍08/16/2019 🔍
08/17/2019 🔍
11/26/2023 🔍
Sources
Advisory: 1915Status: Not defined
Confirmation: 🔍
CVE: CVE-2019-5477 (🔍)
GCVE (CVE): GCVE-0-2019-5477
GCVE (VulDB): GCVE-100-140268
Entry
Created: 08/17/2019 08:40Updated: 11/26/2023 12:33
Changes: 08/17/2019 08:40 (57), 07/30/2020 09:10 (1), 11/26/2023 12:25 (4), 11/26/2023 12:33 (1)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.