Skip to content

fix: address CVEs in http-proxy-middleware #1478

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

Antonio-Maranhao
Copy link
Contributor

Overview

Address CVEs in http-proxy-middleware identified by npm audit

http-proxy-middleware  <=2.0.8
Severity: moderate
http-proxy-middleware allows fixRequestBody to proceed even if bodyParser has failed - https://github.com/advisories/GHSA-9gqv-wp59-fq42
http-proxy-middleware can call writeBody twice because "else if" is not used - https://github.com/advisories/GHSA-4www-5p9h-95mh

Testing recommendations

CI passes

GitHub issue number

n/a

Related Pull Requests

n/a

Checklist

  • Code is written and works correctly;
  • Changes are covered by tests;
  • Documentation reflects the changes;
  • Update rebar.config.script with the correct tag once a new Fauxton release is made

@Antonio-Maranhao Antonio-Maranhao force-pushed the fix-http-proxy-middleware-cve branch from d2ce936 to 50d17d6 Compare April 24, 2025 13:26
@Antonio-Maranhao Antonio-Maranhao merged commit 10001ce into apache:main Apr 24, 2025
3 checks passed
@Antonio-Maranhao Antonio-Maranhao deleted the fix-http-proxy-middleware-cve branch April 24, 2025 16:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants