Machine-In-The-Middle in https-proxy-agent
Priority LOW 38CWE-300Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
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.
Why it matters now
Fix Fixed https-proxy-agent (npm): 2.2.3
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | https-proxy-agent (npm) | before 2.2.3 | 2.2.3 | Patch available | GHSA-pc5p-h8pf-mvwp |
- https-proxy-agent (npm) Vendor— Affected before 2.2.3 Fixed in 2.2.3 Patch available GHSA-pc5p-h8pf-mvwp
Remediation
- Fix · GHSA-pc5p-h8pf-mvwp https-proxy-agent (npm) Fixed in 2.2.3 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-pc5p-h8pf-mvwp
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences