pidusage vulnerabilities and fixes

Q: How do I fix pidusage 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.

Q: Is pidusage being exploited right now?

None of the tracked pidusage CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Q: Which pidusage CVE should I patch first?

CVE-2017-1000220 currently ranks highest (67/100): soyuka/pidusage <=1.1.4 is vulnerable to command injection in the module resulting in arbitrary command execut.

Recent CVEs affecting pidusage, with upgrade or downgrade steps. 1 tracked.

pidusage has 1 tracked vulnerability, 1 critical. A fixed release or vendor patch exists for 1. Most recent: 2017-11-17. Highest priority: CVE-2017-1000220 (score 67/100).

CVE-2017-1000220 CRITICAL 9.8 UPGRADE soyuka/pidusage <=1.1.4 is vulnerable to command injection in the module resulting in arbitrary command execut

FAQ

How do I fix pidusage 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 pidusage being exploited right now?

None of the tracked pidusage CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which pidusage CVE should I patch first?

CVE-2017-1000220 currently ranks highest (67/100): soyuka/pidusage <=1.1.4 is vulnerable to command injection in the module resulting in arbitrary command execut.

← Back to latest CVEs