Skip to content

paranoid2 gem Code backdoor

Critical severity GitHub Reviewed Published Jul 16, 2019 to the GitHub Advisory Database • Updated Aug 29, 2023

Package

bundler paranoid2 (RubyGems)

Affected versions

= 1.1.6

Patched versions

None

Description

The paranoid2 gem 1.1.6 for Ruby, as distributed on RubyGems.org, included a code-execution backdoor inserted by a third party. The current version, without this backdoor, is 1.1.5.

References

Published by the National Vulnerability Database Jul 14, 2019
Reviewed Jul 15, 2019
Published to the GitHub Advisory Database Jul 16, 2019
Last updated Aug 29, 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.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

1.823%
(88th percentile)

Weaknesses

CVE ID

CVE-2019-13589

GHSA ID

GHSA-4g4c-8gqh-m4vm

Source code

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