PatchTheCVEcron vulnerabilities and fixes
Recent CVEs affecting cron, with upgrade or downgrade steps. 4 tracked.
cron has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 3. Most recent: 2019-03-12. Highest priority: CVE-2017-9525 (score 40/100).
- CVE-2019-9706 MEDIUM 5.5 DOWNGRADE MITIGATE Vixie Cron before the 3.0pl1-133 Debian package allows local users to cause a denial of service (use-after-fre
- CVE-2019-9705 MEDIUM 5.5 UPGRADE MITIGATE Vixie Cron before the 3.0pl1-133 Debian package allows local users to cause a denial of service (memory consum
- CVE-2019-9704 MEDIUM 5.5 UPGRADE MITIGATE Vixie Cron before the 3.0pl1-133 Debian package allows local users to cause a denial of service (daemon crash)
- CVE-2017-9525 MEDIUM 6.7 UPGRADE MITIGATE In the cron package through 3.0pl1-128 on Debian, and through 3.0pl1-128ubuntu2 on Ubuntu, the postinst mainta
FAQ
How do I fix cron 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 cron being exploited right now?
None of the tracked cron CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which cron CVE should I patch first?
CVE-2017-9525 currently ranks highest (40/100): In the cron package through 3.0pl1-128 on Debian, and through 3.0pl1-128ubuntu2 on Ubuntu, the postinst mainta.