PatchTheCVEparanoid2 vulnerabilities and fixes
Recent CVEs affecting paranoid2, with upgrade or downgrade steps. 1 tracked.
paranoid2 has 1 tracked vulnerability, 1 critical. A fixed release or vendor patch exists for 0. Most recent: 2019-07-14. Highest priority: CVE-2019-13589 (score 67/100).
- CVE-2019-13589 CRITICAL 9.8 DOWNGRADE The paranoid2 gem 1.1.6 for Ruby, as distributed on RubyGems.org, included a code-execution backdoor inserted
FAQ
How do I fix paranoid2 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 paranoid2 being exploited right now?
None of the tracked paranoid2 CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which paranoid2 CVE should I patch first?
CVE-2019-13589 currently ranks highest (67/100): The paranoid2 gem 1.1.6 for Ruby, as distributed on RubyGems.org, included a code-execution backdoor inserted .