CVE-2022-0155 Vulnerability Analysis & Exploit Details

CVE-2022-0155
Vulnerability Scoring

6.5
/10
High Risk

If left unpatched, CVE-2022-0155 could lead to major system disruptions or data loss.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: Required
    User interaction is necessary for successful exploitation.

CVE-2022-0155 Details

Status: Modified

Last updated: 🕡 21 Nov 2024, 06:38 UTC
Originally published on: 🕗 10 Jan 2022, 20:15 UTC

Time between publication and last update: 1045 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

CVE-2022-0155 Vulnerability Summary

CVE-2022-0155: follow-redirects is vulnerable to Exposure of Private Personal Information to an Unauthorized Actor

Assessing the Risk of CVE-2022-0155

Access Complexity Graph

The exploitability of CVE-2022-0155 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2022-0155

With low attack complexity and no required privileges, CVE-2022-0155 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2022-0155, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2022-0155, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2022-0155 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: None
    CVE-2022-0155 poses no threat to data integrity.
  • Availability: None
    CVE-2022-0155 does not impact system availability.

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.161% (probability of exploit)

EPSS Percentile: 53.94% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 46.06% of others.

CVE-2022-0155 References

External References

CWE Common Weakness Enumeration

CWE-359

CAPEC Common Attack Pattern Enumeration and Classification

  • Evercookie CAPEC-464 An attacker creates a very persistent cookie that stays present even after the user thinks it has been removed. The cookie is stored on the victim's machine in over ten places. When the victim clears the cookie cache via traditional means inside the browser, that operation removes the cookie from certain places but not others. The malicious code then replicates the cookie from all of the places where it was not deleted to all of the possible storage locations once again. So the victim again has the cookie in all of the original storage locations. In other words, failure to delete the cookie in even one location will result in the cookie's resurrection everywhere. The evercookie will also persist across different browsers because certain stores (e.g., Local Shared Objects) are shared between different browsers.
  • Cross Site Identification CAPEC-467 An attacker harvests identifying information about a victim via an active session that the victim's browser has with a social networking site. A victim may have the social networking site open in one tab or perhaps is simply using the "remember me" feature to keep their session with the social networking site active. An attacker induces a payload to execute in the victim's browser that transparently to the victim initiates a request to the social networking site (e.g., via available social network site APIs) to retrieve identifying information about a victim. While some of this information may be public, the attacker is able to harvest this information in context and may use it for further attacks on the user (e.g., spear phishing).
  • Probe iOS Screenshots CAPEC-498 An adversary examines screenshot images created by iOS in an attempt to obtain sensitive information. This attack targets temporary screenshots created by the underlying OS while the application remains open in the background.
  • Shoulder Surfing CAPEC-508 In a shoulder surfing attack, an adversary observes an unaware individual's keystrokes, screen content, or conversations with the goal of obtaining sensitive information. One motive for this attack is to obtain sensitive information about the target for financial, personal, political, or other gains. From an insider threat perspective, an additional motive could be to obtain system/application credentials or cryptographic keys. Shoulder surfing attacks are accomplished by observing the content "over the victim's shoulder", as implied by the name of this attack.

Vulnerable Configurations

  • cpe:2.3:a:follow-redirects_project:follow-redirects:0.0.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:0.0.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:0.0.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:0.0.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:0.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:0.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:0.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:0.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:0.3.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:0.3.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.2.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.2.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.2.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.2.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.2.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.2.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.2.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.2.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.2.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.2.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.2.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.2.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.3.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.3.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.4.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.4.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.4.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.4.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.5.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.5.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.5.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.5.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.5.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.5.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.5.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.5.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.5.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.5.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.5.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.5.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.5.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.5.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.5.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.5.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.5.8:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.5.8:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.5.9:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.5.9:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.5.10:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.5.10:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.6.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.6.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.6.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.6.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.7.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.7.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.8.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.8.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.8.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.8.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.9.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.9.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.9.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.9.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.10.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.10.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.11.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.11.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.12.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.12.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.12.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.12.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.13.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.13.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.13.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.13.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.13.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.13.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.13.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.13.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.14.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.14.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.14.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.14.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.14.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.14.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.14.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.14.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.14.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.14.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.14.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.14.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:follow-redirects_project:follow-redirects:1.14.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:follow-redirects_project:follow-redirects:1.14.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:siemens:sinec_ins:-:*:*:*:*:*:*:*
    cpe:2.3:a:siemens:sinec_ins:-:*:*:*:*:*:*:*
  • cpe:2.3:a:siemens:sinec_ins:1.0:-:*:*:*:*:*:*
    cpe:2.3:a:siemens:sinec_ins:1.0:-:*:*:*:*:*:*
  • cpe:2.3:a:siemens:sinec_ins:1.0:sp1:*:*:*:*:*:*
    cpe:2.3:a:siemens:sinec_ins:1.0:sp1:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2022-0155: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-2129 – A vulnerability was found in Mage AI 0.9.75. It has been classified as problematic. This affects an unknown part. The manipulation leads to insecur...
  • CVE-2025-2127 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla. It has been classified as problematic. Affected is an unknown function of th...
  • CVE-2025-2126 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla and classified as critical. This issue affects some unknown processing of the...
  • CVE-2025-2125 – A vulnerability has been found in Control iD RH iD 25.2.25.0 and classified as problematic. This vulnerability affects unknown code of the file /v2...
  • CVE-2025-2124 – A vulnerability, which was classified as problematic, was found in Control iD RH iD 25.2.25.0. This affects an unknown part of the file /v2/custome...