# CVE-2022-0155: Exposure of Private Personal Information to an Unauthorized Actor in follow-redirects/follow-redirects

> An attacker can expose private personal information to unauthorized actors via the follow-redirects library.

- **Severity:** High 8.0 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 10 Jan 2022
- **Updated:** 2 Aug 2024
- **Also known as:** AZL-44112, CLSA-2026-1784596354, DEBIAN-CVE-2022-0155, GHSA-74fj-2j2h-c42q, UBUNTU-CVE-2022-0155

## What is CVE-2022-0155?

CVE-2022-0155 is a high-severity vulnerability in follow-redirects/follow-redirects, published on 10 Jan 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

follow-redirects is vulnerable to Exposure of Private Personal Information to an Unauthorized Actor

Weakness: CWE-359 (Exposure of Private Personal Information to an Unauthorized Actor)

## Which versions are affected by CVE-2022-0155?

2 open source packages ship an affected version, including follow-redirects. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `follow-redirects` | npm | All versions | 1.14.7 |
| `follow-redirects` | npm | All versions | 1.14.7 |

Products: Follow-Redirects Project Follow-Redirects, Siemens Sinec Ins.

## How do I fix CVE-2022-0155?

Upgrade follow-redirects to 1.14.7 or later.

## Is CVE-2022-0155 being exploited?

There is no known exploitation of CVE-2022-0155 in the wild and no public exploit code.

Public exploit code:

- https://github.com/coana-tech/CVE-2022-0155-PoC (github_poc): https://github.com/coana-tech/CVE-2022-0155-PoC

## Other vulnerabilities in follow-redirects/follow-redirects

- [CVE-2026-40895](https://insights.sbomify.com/CVE-2026-40895/): follow-redirects: Custom Authentication Headers Leaked to Cross-Domain Redirect Targets (medium 6.9)
- [CVE-2024-28849](https://insights.sbomify.com/CVE-2024-28849/): Proxy-Authorization header kept across hosts in follow-redirects (medium 6.5)
- [CVE-2022-0536](https://insights.sbomify.com/CVE-2022-0536/): Improper Removal of Sensitive Information Before Storage or Transfer in follow-redirects/follow-redirects (low 2.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-0155 and fix it if it is affected.

What it is: CVE-2022-0155 is a high-severity vulnerability in follow-redirects/follow-redirects, published on 10 Jan 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-0155 in the wild and no public exploit code.

Affected packages and fixed versions:
- follow-redirects (npm): affected all versions; fixed in 1.14.7
- follow-redirects (npm): affected all versions; fixed in 1.14.7

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-0155/ (Markdown: https://insights.sbomify.com/CVE-2022-0155/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-0155
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-0155
- OSV: https://osv.dev/vulnerability/CVE-2022-0155

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-0155/
Summaries are generated and may contain mistakes; the official description above is the record.