paranoidhttp vulnerabilities and fixes
Recent CVEs affecting paranoidhttp, with upgrade or downgrade steps. 1 tracked.
paranoidhttp has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2023-01-30. Highest priority: CVE-2023-24623 (score 44/100).
- CVE-2023-24623 HIGH 7.5 UPGRADE Paranoidhttp before 0.3.0 allows SSRF because [::] is equivalent to the 127.0.0.1 address, but does not match
FAQ
How do I fix paranoidhttp 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 paranoidhttp being exploited right now?
None of the tracked paranoidhttp CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which paranoidhttp CVE should I patch first?
CVE-2023-24623 currently ranks highest (44/100): Paranoidhttp before 0.3.0 allows SSRF because [::] is equivalent to the 127.0.0.1 address, but does not match .