sentinel vulnerabilities
Recent CVEs affecting sentinel products. 5 tracked.
sentinel has 5 tracked vulnerabilities, 3 critical. A fixed release or vendor patch exists for 5. Most recent: 2017-10-04. Highest priority: CVE-2017-12821 (score 61/100).
- CVE-2017-12822 CRITICAL 9.9 UPGRADE Remote enabling and disabling admin interface in Gemalto's HASP SRM, Sentinel HASP and Sentinel LDK products p
- CVE-2017-12821 CRITICAL 9.8 UPGRADE Memory corruption in Gemalto's HASP SRM, Sentinel HASP and Sentinel LDK products prior to Sentinel LDK RTE ver
- CVE-2017-12820 HIGH 7.5 UPGRADE Arbitrary memory read from controlled memory pointer in Gemalto's HASP SRM, Sentinel HASP and Sentinel LDK pro
- CVE-2017-12819 CRITICAL 9.8 UPGRADE Remote manipulations with language pack updater lead to NTLM-relay attack for system user in Gemalto's HASP SR
- CVE-2017-12818 HIGH 7.5 UPGRADE Stack overflow in custom XML-parser in Gemalto's HASP SRM, Sentinel HASP and Sentinel LDK products prior to Se
FAQ
How do I fix sentinel 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 sentinel being exploited right now?
None of the tracked sentinel CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which sentinel CVE should I patch first?
CVE-2017-12821 currently ranks highest (61/100): Memory corruption in Gemalto's HASP SRM, Sentinel HASP and Sentinel LDK products prior to Sentinel LDK RTE ver.