parse-url vulnerabilities and fixes

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

Also searched as: parse url.

parse-url has 6 tracked vulnerabilities, 2 critical. A fixed release or vendor patch exists for 6. Most recent: 2022-09-15. Highest priority: CVE-2022-2216 (score 64/100).

• CVE-2022-3224 MEDIUM 6.1 UPGRADE Misinterpretation of Input in GitHub repository ionicabizau/parse-url prior to 8.1.0.
• CVE-2022-2900 CRITICAL 9.1 UPGRADE Server-Side Request Forgery (SSRF) in GitHub repository ionicabizau/parse-url prior to 8.1.0.
• CVE-2022-2218 MEDIUM 6.1 UPGRADE Cross-site Scripting (XSS) - Stored in GitHub repository ionicabizau/parse-url prior to 7.0.0.
• CVE-2022-2217 MEDIUM 6.1 UPGRADE Cross-site Scripting (XSS) - Generic in GitHub repository ionicabizau/parse-url prior to 7.0.0.
• CVE-2022-2216 CRITICAL 9.8 UPGRADE Server-Side Request Forgery (SSRF) in GitHub repository ionicabizau/parse-url prior to 7.0.0.
• CVE-2022-0722 HIGH 7.5 UPGRADE Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository ionicabizau/parse-url prior to

FAQ

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

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

Which parse-url CVE should I patch first?

CVE-2022-2216 currently ranks highest (64/100): Server-Side Request Forgery (SSRF) in GitHub repository ionicabizau/parse-url prior to 7.0.0..

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