# GHSA-pc5p-h8pf-mvwp: Machine-In-The-Middle in https-proxy-agent

> Attackers can intercept unencrypted traffic via MITM if the proxy returns non-200 status, exposing sensitive data like credentials.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Apr 2020

## What is GHSA-pc5p-h8pf-mvwp?

GHSA-pc5p-h8pf-mvwp is a vulnerability in https-proxy-agent, published on 16 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Versions of `https-proxy-agent` prior to 2.2.3 are vulnerable to Machine-In-The-Middle. The package fails to enforce TLS on the socket if the proxy server responds the to the request with a HTTP status different than 200. This allows an attacker with access to the proxy server to intercept unencrypted communications, which may include sensitive information such as credentials.

## Recommendation

Upgrade to version 3.0.0 or 2.2.3.

## Which versions are affected by GHSA-pc5p-h8pf-mvwp?

2 open source packages ship an affected version, including https-proxy-agent.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `https-proxy-agent` | npm | All versions | 2.2.3 |
| `https-proxy-agent` | npm | All versions | 2.2.3 |

## How do I fix GHSA-pc5p-h8pf-mvwp?

Upgrade https-proxy-agent to 2.2.3 or later.

## Is GHSA-pc5p-h8pf-mvwp being exploited?

There is no known exploitation of GHSA-pc5p-h8pf-mvwp in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-pc5p-h8pf-mvwp and fix it if it is affected.

What it is: GHSA-pc5p-h8pf-mvwp is a vulnerability in https-proxy-agent, published on 16 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-pc5p-h8pf-mvwp in the wild and no public exploit code.

Affected packages and fixed versions:
- https-proxy-agent (npm): affected all versions; fixed in 2.2.3
- https-proxy-agent (npm): affected all versions; fixed in 2.2.3

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/GHSA-pc5p-h8pf-mvwp/ (Markdown: https://insights.sbomify.com/GHSA-pc5p-h8pf-mvwp/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-pc5p-h8pf-mvwp

---
From sbomify Insights: https://insights.sbomify.com/GHSA-pc5p-h8pf-mvwp/
Summaries are generated and may contain mistakes; the official description above is the record.