CVE-2018-3739: Denial of Service in https-proxy-agent

https-proxy-agent Updated 02 Oct 2025

Summary

27/07/2018
Yes i
Critical
9.1

CVE-2018-3739: Denial of Service in https-proxy-agent. Affects https-proxy-agent versions < 2.2.0. Fixed in 2.2.0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The https-proxy-agent package is an npm package that provides an HTTP(s) proxy agent implementation for Node.js. It allows users to make HTTP requests through a proxy server. The package is widely used in Node.js applications that require proxy support.

Vulnerability Detail

Versions of https-proxy-agent before 2.2.0 are vulnerable to denial of service. The vulnerability arises due to unsanitized options (proxy.auth) being passed to the Buffer() function. An attacker can exploit this vulnerability by sending specially crafted requests, causing the application to crash or become unresponsive. This can lead to a denial of service condition, impacting the availability of the affected application.

How To Fix

Latest published version: 9.1.0 as of 22 Oct 2026

npm install https-proxy-agent@9.1.0

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.2.0

This is the first release that contains the fix.

npm install https-proxy-agent@2.2.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to update to the fixed version of the package.

Conclusion

In conclusion, the https-proxy-agent package versions prior to 2.2.0 are vulnerable to a denial of service attack. It is crucial to update to version 2.2.0 or later to mitigate this vulnerability. For additional assistance with vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for https-proxy-agent →

Share this vulnerability

FAQ

The vulnerability can be exploited by an attacker to cause a denial of service, making the affected application unresponsive or crash.

You can use Vulert's playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Vulert analyzes the package-lock.json file to identify and alert in real-time for open-source vulnerabilities.

Yes, updating the https-proxy-agent package to version 2.2.0 or later will fix this vulnerability.

No, there are no known workarounds for this vulnerability. Updating to the fixed version is the recommended solution.

For further support on vulnerability remediation, you can reach out to info@devnack.com.

Related vulnerabilities

Recent vulnerabilities recorded for https-proxy-agent.

How To Fix

Latest published version: 9.1.0 as of 22 Oct 2026

npm install https-proxy-agent@9.1.0

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.2.0

This is the first release that contains the fix.

npm install https-proxy-agent@2.2.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback