PatchTheCVEradicale vulnerabilities and fixes
Recent CVEs affecting radicale, with upgrade or downgrade steps. 4 tracked.
radicale has 4 tracked vulnerabilities, 2 critical. A fixed release or vendor patch exists for 4. Most recent: 2017-04-30. Highest priority: CVE-2015-8747 (score 67/100).
- CVE-2017-8342 HIGH 8.1 UPGRADE Radicale before 1.1.2 and 2.x before 2.0.0rc2 is prone to timing oracles and simple brute-force attacks when u
- CVE-2016-1505 CRITICAL 10.0 UPGRADE The filesystem storage backend in Radicale before 1.1 on Windows allows remote attackers to read or write to a
- CVE-2015-8748 MEDIUM 5.3 UPGRADE Radicale before 1.1 allows remote authenticated users to bypass owner_write and owner_only limitations via reg
- CVE-2015-8747 CRITICAL 10.0 UPGRADE The multifilesystem storage backend in Radicale before 1.1 allows remote attackers to read or write to arbitra
FAQ
How do I fix radicale 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 radicale being exploited right now?
None of the tracked radicale CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which radicale CVE should I patch first?
CVE-2015-8747 currently ranks highest (67/100): The multifilesystem storage backend in Radicale before 1.1 allows remote attackers to read or write to arbitra.