PatchTheCVEmeteocontrol vulnerabilities
Recent CVEs affecting meteocontrol products. 4 tracked.
meteocontrol has 4 tracked vulnerabilities, 3 critical. A fixed release or vendor patch exists for 0. Most recent: 2017-03-21. Highest priority: CVE-2016-2298 (score 69/100).
- CVE-2016-4504 HIGH 8.8 MITIGATE A Cross-Site Request Forgery issue was discovered in Meteocontrol WEB'log Basic 100 all versions, Light all ve
- CVE-2016-2298 CRITICAL 9.8 MITIGATE MITIGATE Meteocontrol WEB'log Basic 100, Light, Pro, and Pro Unlimited allows remote attackers to obtain sensitive clea
- CVE-2016-2297 CRITICAL 9.4 MITIGATE MITIGATE Meteocontrol WEB'log Basic 100, Light, Pro, and Pro Unlimited allows remote attackers to execute arbitrary com
- CVE-2016-2296 CRITICAL 9.4 MITIGATE MITIGATE Meteocontrol WEB'log Basic 100, Light, Pro, and Pro Unlimited does not require authentication for "post-admin"
FAQ
How do I fix meteocontrol 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 meteocontrol being exploited right now?
None of the tracked meteocontrol CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which meteocontrol CVE should I patch first?
CVE-2016-2298 currently ranks highest (69/100): Meteocontrol WEB'log Basic 100, Light, Pro, and Pro Unlimited allows remote attackers to obtain sensitive clea.