PatchTheCVEperltidy vulnerabilities and fixes
Recent CVEs affecting perltidy, with upgrade or downgrade steps. 2 tracked.
perltidy has 2 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 2. Most recent: 2017-10-17. Highest priority: CVE-2014-2277 (score 32/100).
- CVE-2016-10374 MEDIUM 5.5 UPGRADE perltidy through 20160302, as used by perlcritic, check-all-the-things, and other software, relies on the curr
- CVE-2014-2277 HIGH 7.1 UPGRADE The make_temporary_filename function in perltidy 20120701-1 and earlier allows local users to obtain sensitive
FAQ
How do I fix perltidy 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 perltidy being exploited right now?
None of the tracked perltidy CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which perltidy CVE should I patch first?
CVE-2014-2277 currently ranks highest (32/100): The make_temporary_filename function in perltidy 20120701-1 and earlier allows local users to obtain sensitive.