PatchTheCVEaws-lambda-multipart-parser vulnerabilities and fixes
Recent CVEs affecting aws-lambda-multipart-parser, with upgrade or downgrade steps. 1 tracked.
Also searched as: aws lambda multipart parser.
aws-lambda-multipart-parser has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2018-03-04. Highest priority: CVE-2018-7560 (score 54/100).
- CVE-2018-7560 HIGH 7.5 UPGRADE index.js in the Anton Myshenin aws-lambda-multipart-parser NPM package before 0.1.2 has a Regular Expression D
FAQ
How do I fix aws-lambda-multipart-parser vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is aws-lambda-multipart-parser being exploited right now?
None of the tracked aws-lambda-multipart-parser CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which aws-lambda-multipart-parser CVE should I patch first?
CVE-2018-7560 currently ranks highest (54/100): index.js in the Anton Myshenin aws-lambda-multipart-parser NPM package before 0.1.2 has a Regular Expression D.