Skip to content

Information disclosure issue in Active Resource

High severity GitHub Reviewed Published May 21, 2020 to the GitHub Advisory Database • Updated Jan 23, 2023

Package

bundler activeresource (RubyGems)

Affected versions

< 5.1.1

Patched versions

5.1.1

Description

There is a possible information disclosure issue in Active Resource <v5.1.1 that could allow an attacker to create specially crafted requests to access data in an unexpected way and possibly leak information.

References

Published by the National Vulnerability Database May 12, 2020
Reviewed May 21, 2020
Published to the GitHub Advisory Database May 21, 2020
Last updated Jan 23, 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
High
Integrity
None
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:H/I:N/A:N

EPSS score

0.178%
(55th percentile)

Weaknesses

CVE ID

CVE-2020-8151

GHSA ID

GHSA-46j2-xjgp-jrfm

Source code

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