PatchTheCVEgetcujo vulnerabilities
Recent CVEs affecting getcujo products. 7 tracked.
getcujo has 7 tracked vulnerabilities, 3 critical. A fixed release or vendor patch exists for 0. Most recent: 2019-10-31. Highest priority: CVE-2018-4031 (score 66/100).
- CVE-2018-4031 CRITICAL 10.0 DOWNGRADE An exploitable vulnerability exists in the safe browsing function of the CUJO Smart Firewall, version 7003
- CVE-2018-4030 HIGH 7.5 DOWNGRADE An exploitable vulnerability exists the safe browsing function of the CUJO Smart Firewall, version 7003
- CVE-2018-4011 HIGH 7.5 DOWNGRADE An exploitable integer underflow vulnerability exists in the mdnscap binary of the CUJO Smart Firewall, versio
- CVE-2018-4003 CRITICAL 9.8 DOWNGRADE An exploitable heap overflow vulnerability exists in the mdnscap binary of the CUJO Smart Firewall running fir
- CVE-2018-3985 CRITICAL 9.8 DOWNGRADE An exploitable double free vulnerability exists in the mdnscap binary of the CUJO Smart Firewall
- CVE-2018-3969 HIGH 7.8 DOWNGRADE An exploitable vulnerability exists in the verified boot protection of the CUJO Smart Firewall
- CVE-2018-3963 HIGH 8.0 DOWNGRADE An exploitable command injection vulnerability exists in the DHCP daemon configuration of the CUJO Smart Firew
FAQ
How do I fix getcujo 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 getcujo being exploited right now?
None of the tracked getcujo CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which getcujo CVE should I patch first?
CVE-2018-4031 currently ranks highest (66/100): An exploitable vulnerability exists in the safe browsing function of the CUJO Smart Firewall, version 7003.