PatchTheCVErecurly vulnerabilities
Recent CVEs affecting recurly products. 3 tracked.
recurly has 3 tracked vulnerabilities, 3 critical. A fixed release or vendor patch exists for 1. Most recent: 2017-11-13. Highest priority: CVE-2017-0907 (score 61/100).
- CVE-2017-0907 CRITICAL 9.8 DOWNGRADE The Recurly Client .NET Library before 1.0.1, 1.1.10, 1.2.8, 1.3.2, 1.4.14, 1.5.3, 1.6.2, 1.7.1, 1.8.1 is vuln
- CVE-2017-0906 CRITICAL 9.8 UPGRADE The Recurly Client Python Library before 2.0.5, 2.1.16, 2.2.22, 2.3.1, 2.4.5, 2.5.1, 2.6.2 is vulnerable to a
- CVE-2017-0905 CRITICAL 9.8 DOWNGRADE The Recurly Client Ruby Library before 2.0.13, 2.1.11, 2.2.5, 2.3.10, 2.4.11, 2.5.4, 2.6.3, 2.7.8, 2.8.2, 2.9.
FAQ
How do I fix recurly 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 recurly being exploited right now?
None of the tracked recurly CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which recurly CVE should I patch first?
CVE-2017-0907 currently ranks highest (61/100): The Recurly Client .NET Library before 1.0.1, 1.1.10, 1.2.8, 1.3.2, 1.4.14, 1.5.3, 1.6.2, 1.7.1, 1.8.1 is vuln.