Skip to content

RubyGems Escape sequence injection vulnerability in verbose

High severity GitHub Reviewed Published Jun 20, 2019 to the GitHub Advisory Database • Updated Aug 28, 2023

Package

bundler rubygems-update (RubyGems)

Affected versions

>= 2.6.0, < 2.7.9
>= 3.0.0, < 3.0.2

Patched versions

2.7.9
3.0.2

Description

An issue was discovered in RubyGems 2.6 and later through 3.0.2. Since Gem::UserInteraction#verbose calls say without escaping, escape sequence injection is possible.

References

Reviewed Jun 20, 2019
Published to the GitHub Advisory Database Jun 20, 2019
Last updated Aug 28, 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
None
Integrity
High
Availability
None

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

EPSS score

0.201%
(59th percentile)

Weaknesses

CVE ID

CVE-2019-8321

GHSA ID

GHSA-fr32-gr5c-xq5c

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.