PatchTheCVEeviewgps vulnerabilities
Recent CVEs affecting eviewgps products. 3 tracked.
eviewgps has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2017-03-27. Highest priority: CVE-2017-5237 (score 51/100).
- CVE-2017-5239 HIGH 7.5 MITIGATE Due to a lack of standard encryption when transmitting sensitive information over the internet to a centralize
- CVE-2017-5238 MEDIUM 5.3 MITIGATE Due to a lack of bounds checking, several input configuration fields for the Eview EV-07S GPS Tracker will ove
- CVE-2017-5237 HIGH 7.5 MITIGATE Due to a lack of authentication, an unauthenticated user who knows the Eview EV-07S GPS Tracker's phone number
FAQ
How do I fix eviewgps 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 eviewgps being exploited right now?
None of the tracked eviewgps CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which eviewgps CVE should I patch first?
CVE-2017-5237 currently ranks highest (51/100): Due to a lack of authentication, an unauthenticated user who knows the Eview EV-07S GPS Tracker's phone number.