Skip to content

Exposure of sensitive information in follow-redirects

High severity GitHub Reviewed Published Jan 12, 2022 to the GitHub Advisory Database • Updated Nov 29, 2023

Package

npm follow-redirects (npm)

Affected versions

< 1.14.7

Patched versions

1.14.7
Published by the National Vulnerability Database Jan 10, 2022
Reviewed Jan 11, 2022
Published to the GitHub Advisory Database Jan 12, 2022
Last updated Nov 29, 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
Low
User interaction
Required
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:L/UI:R/S:U/C:H/I:H/A:H

EPSS score

0.156%
(53rd percentile)

Weaknesses

CVE ID

CVE-2022-0155

GHSA ID

GHSA-74fj-2j2h-c42q
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.