whereis vulnerabilities and fixes

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

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

Q: Which whereis CVE should I patch first?

CVE-2018-3772 currently ranks highest (66/100): Concatenating unsanitized user input in the `whereis` npm module < 0.4.1 allowed an attacker to execute arbitr.

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

whereis has 1 tracked vulnerability, 1 critical. A fixed release or vendor patch exists for 1. Most recent: 2018-07-30. Highest priority: CVE-2018-3772 (score 66/100).

CVE-2018-3772 CRITICAL 9.8 UPGRADE Concatenating unsanitized user input in the `whereis` npm module < 0.4.1 allowed an attacker to execute arbitr

FAQ

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

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

Which whereis CVE should I patch first?

CVE-2018-3772 currently ranks highest (66/100): Concatenating unsanitized user input in the `whereis` npm module < 0.4.1 allowed an attacker to execute arbitr.

← Back to latest CVEs