PatchTheCVEtodd miller vulnerabilities
Recent CVEs affecting todd miller products. 7 tracked.
todd miller has 7 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 5. Most recent: 2017-04-14. Highest priority: CVE-2013-1775 (score 51/100).
- CVE-2016-7032 HIGH 7.0 MITIGATE sudo_noexec.so in Sudo before 1.8.15 on Linux might allow local users to bypass intended noexec command restri
- CVE-2014-0106 MEDIUM 6.6 UPGRADE MITIGATE Sudo 1.6.9 before 1.8.5, when env_reset is disabled, does not properly check environment variables for the env
- CVE-2013-2777 MEDIUM 4.4 UPGRADE UPGRADE sudo before 1.7.10p5 and 1.8.x before 1.8.6p6, when the tty_tickets option is enabled, does not properly valid
- CVE-2013-2776 MEDIUM 4.4 MITIGATE UPGRADE sudo 1.3.5 through 1.7.10p5 and 1.8.0 through 1.8.6p6, when running on systems without /proc or the sysctl fun
- CVE-2013-1776 MEDIUM 4.4 UPGRADE MITIGATE sudo 1.3.5 through 1.7.10 and 1.8.0 through 1.8.5, when the tty_tickets option is enabled, does not properly v
- CVE-2013-1775 MEDIUM 6.9 MITIGATE UPGRADE sudo 1.6.0 through 1.7.10p6 and sudo 1.8.0 through 1.8.6p6 allows local users or physically proximate attacker
- CVE-2012-3440 MEDIUM 5.6 MITIGATE MITIGATE A certain Red Hat script for sudo 1.7.2 on Red Hat Enterprise Linux (RHEL) 5 allows local users to overwrite a
FAQ
How do I fix todd miller 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 todd miller being exploited right now?
None of the tracked todd miller CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which todd miller CVE should I patch first?
CVE-2013-1775 currently ranks highest (51/100): sudo 1.6.0 through 1.7.10p6 and sudo 1.8.0 through 1.8.6p6 allows local users or physically proximate attacker.