http-proxy-middleware vulnerabilities
The one-liner node.js proxy middleware for connect, express, next.js and more
- Registry
- npm
- Latest
- 4.2.0
- License
- MIT
5 known advisories
The latest version, 4.2.0, is not affected by any of them. Projects on older versions may be.
npm install http-proxy-middleware@4.2.0Security advisories for http-proxy-middleware
http-proxy-middleware: multipart/form-data field injection via unescaped CRLF in `fixRequestBody`
- Affected
- >=3.0.4 <3.0.7 · >=4.0.0 <4.1.1
- Fixed in
- 3.0.7, 4.1.1
http-proxy-middleware `router` host+path substring matching allows Host-header-driven backend routing bypass
- Affected
- >=3.0.0 <3.0.6 · >=4.0.0 <4.1.0 · >=0.16.0 <2.0.10
- Fixed in
- 2.0.10, 3.0.6, 4.1.0
http-proxy-middleware can call writeBody twice because "else if" is not used
- Affected
- >=1.3.0 <2.0.8 · >=3.0.0 <3.0.4
- Fixed in
- 2.0.8, 3.0.4
http-proxy-middleware allows fixRequestBody to proceed even if bodyParser has failed
- Affected
- >=1.3.0 <2.0.9 · >=3.0.0 <3.0.5
- Fixed in
- 2.0.9, 3.0.5
Denial of service in http-proxy-middleware
- Affected
- <2.0.7 · >=3.0.0 <3.0.3
- Fixed in
- 2.0.7, 3.0.3
Which of your client projects still run an old http-proxy-middleware?
NPMscan reads the package-lock.json, yarn.lock and pnpm-lock.yaml in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other npm packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the npm registry.