How severe is GHSA-8w57-jfpm-945m?

No CVSS score has been assigned to GHSA-8w57-jfpm-945m yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-8w57-jfpm-945m?

GHSA-8w57-jfpm-945m affects the following packages: http-proxy-agent (npm). Ecosystems affected: npm.

How do I fix GHSA-8w57-jfpm-945m?

Update http-proxy-agent to 2.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8w57-jfpm-945m is resolved across your whole dependency graph.

How do I detect GHSA-8w57-jfpm-945m in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for http-proxy-agent. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-8w57-jfpm-945m if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-8w57-jfpm-945m?

O3 pinpoints whether GHSA-8w57-jfpm-945m is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-8w57-jfpm-945m actively exploited in the wild?

No public exploit code has been indexed for GHSA-8w57-jfpm-945m yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-8w57-jfpm-945m published, and has it been updated?

GHSA-8w57-jfpm-945m was published on June 11, 2019 and was last updated on April 11, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-8w57-jfpm-945m

GHSA-8w57-jfpm-945m is a security vulnerability in http-proxy-agent. O3 Security confirms whether GHSA-8w57-jfpm-945m is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Denial of Service in http-proxy-agent

Published

Jun 11, 2019

Updated

Apr 11, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Apr 11, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

2Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

http-proxy-agentnpm

141.3Mdownloads / week

Description

Versions of http-proxy-agent before 2.1.0 are vulnerable to denial of service and uninitialized memory leak when unsanitized options are passed to Buffer. An attacker may leverage these unsanitized options to consume system resources.

Recommendation

Update to version 2.1.0 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`http-proxy-agent`	all versions	2.1.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for http-proxy-agent. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update http-proxy-agent to 2.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8w57-jfpm-945m is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-8w57-jfpm-945m is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-8w57-jfpm-945m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Versions of `http-proxy-agent` before 2.1.0 are vulnerable to denial of service and uninitialized memory leak when unsanitized options are passed to `Buffer`. An attacker may leverage these unsanitized options to consume system resources. ## Recommendation Update to version 2.1.0 or later.

O3 Security · Impact-Aware SCA

Is GHSA-8w57-jfpm-945m in your dependencies?

O3 detects GHSA-8w57-jfpm-945m across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works