PatchTheCVEcarlosgavazzi vulnerabilities
Recent CVEs affecting carlosgavazzi products. 5 tracked.
carlosgavazzi has 5 tracked vulnerabilities, 2 critical. A fixed release or vendor patch exists for 2. Most recent: 2017-02-13. Highest priority: CVE-2017-5146 (score 60/100).
- CVE-2017-5146 HIGH 7.5 MITIGATE MITIGATE An issue was discovered in Carlo Gavazzi VMU-C EM prior to firmware Version A11_U05, and VMU-C PV prior to fir
- CVE-2017-5145 CRITICAL 10.0 MITIGATE MITIGATE An issue was discovered in Carlo Gavazzi VMU-C EM prior to firmware Version A11_U05, and VMU-C PV prior to fir
- CVE-2017-5144 CRITICAL 9.8 MITIGATE MITIGATE An issue was discovered in Carlo Gavazzi VMU-C EM prior to firmware Version A11_U05, and VMU-C PV prior to fir
- CVE-2012-6428 HIGH 10.0 UPGRADE MITIGATE The Carlo Gavazzi EOS-Box stores hard-coded passwords in the PHP file of the device
- CVE-2012-6427 HIGH 7.8 UPGRADE MITIGATE The Carlo Gavazzi EOS-Box does not check the validity of the data before executing queries
FAQ
How do I fix carlosgavazzi 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 carlosgavazzi being exploited right now?
None of the tracked carlosgavazzi CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which carlosgavazzi CVE should I patch first?
CVE-2017-5146 currently ranks highest (60/100): An issue was discovered in Carlo Gavazzi VMU-C EM prior to firmware Version A11_U05, and VMU-C PV prior to fir.