url-parse vulnerabilities and fixes

Recent CVEs affecting url-parse, with upgrade or downgrade steps. 6 tracked.

Also searched as: url parse.

url-parse has 6 tracked vulnerabilities, 2 critical. A fixed release or vendor patch exists for 6. Most recent: 2022-02-21. Highest priority: CVE-2022-0691 (score 65/100).

• CVE-2022-0691 CRITICAL 9.8 UPGRADE Authorization Bypass Through User-Controlled Key in NPM url-parse prior to 1.5.9.
• CVE-2022-0686 CRITICAL 9.1 UPGRADE Authorization Bypass Through User-Controlled Key in NPM url-parse prior to 1.5.8.
• CVE-2022-0639 MEDIUM 5.3 UPGRADE Authorization Bypass Through User-Controlled Key in NPM url-parse prior to 1.5.7.
• CVE-2022-0512 MEDIUM 5.3 UPGRADE Authorization Bypass Through User-Controlled Key in NPM url-parse prior to 1.5.6.
• CVE-2021-3664 MEDIUM 5.3 UPGRADE url-parse is vulnerable to URL Redirection to Untrusted Site
• CVE-2021-27515 MEDIUM 5.3 UPGRADE url-parse before 1.5.0 mishandles certain uses of backslash such as http:\/ and interprets the URI as a relati

FAQ

How do I fix url-parse 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 url-parse being exploited right now?

None of the tracked url-parse CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which url-parse CVE should I patch first?

CVE-2022-0691 currently ranks highest (65/100): Authorization Bypass Through User-Controlled Key in NPM url-parse prior to 1.5.9..

RSS feed for url-parse · ← Back to latest CVEs