Patch & vulnerability status
Thales
SafeNet Authentication 10.9.4482.0
Latest tracked version 10.9.4482.0. Release status, tracked CVEs, and automated cross-platform patching for SafeNet Authentication.
Category: Security
| Platform | Latest version | CVEs tracked | Last checked |
|---|---|---|---|
| Windows | 10.9.4482.0 | 4 | 2024-05-20 |
Known vulnerabilities (CVEs) in SafeNet Authentication
Lavawall tracks 4 published CVEs affecting SafeNet Authentication, and deploys the versions that fix them automatically across your fleet.
| CVE | Published | Severity | Details | Vector |
|---|---|---|---|---|
| CVE-2023-7016 | 2024-02-27 11:15:08 | HIGH (8) | A flaw in Thales SafeNet Authentication Client prior to 10.8 R10 on Windows allows an attacker to execute code at a SYSTEM level via local access. | LOCAL |
| CVE-2023-5993 | 2024-02-27 11:15:07 | HIGH (8) | A flaw in the Windows Installer in Thales SafeNet Authentication Client prior to 10.8 R10 on Windows allows an attacker to escalate their privilege level via local access. | LOCAL |
| CVE-2021-42056 | 2022-06-24 17:15:08 | MEDIUM (7) | Thales Safenet Authentication Client (SAC) for Linux and Windows through 10.7.7 creates insecure temporary hid and lock files allowing a local attacker, through a symlink attack, to overwrite arbitrary files, and potentially achieve arbitrary command execution with high privileges. | LOCAL |
| CVE-2015-7596 | 2018-03-02 22:29:00 | MEDIUM (5) | SafeNet Authentication Service End User Software Tools for Windows uses a weak ACL for unspecified installation directories and executable modules, which allows local users to gain privileges by modifying an executable module. | LOCAL |
Why keeping SafeNet Authentication patched matters
Unpatched third-party applications are one of the most common ways attackers get in: 57% of breached MSP clients and 32% of ransomware cases trace back to a missing patch. Every SafeNet Authentication release that fixes a security bug is public, so attackers see it too, and an out-of-date install becomes a documented way in. Tracking the installed version on every machine and closing the gap quickly is what turns a disclosed CVE into a non-event.
How Lavawall® patches SafeNet Authentication
Lavawall® watches SafeNet Authentication releases and CVEs continuously, ranks each update by risk, and deploys it across your whole fleet, Windows, macOS, and Linux, from a single agent, independently of your RMM. You get one place to see which machines are behind on SafeNet Authentication, one policy to bring them current, and timestamped evidence for audits.
Frequently asked questions
Lavawall tracks SafeNet Authentication at version 10.9.4482.0 (last checked 2024-05-20). New releases are monitored continuously and can be deployed automatically across your fleet.
Lavawall tracks 4 CVEs for SafeNet Authentication and remediates them automatically as part of patching.
Deploy the Lavawall® agent and SafeNet Authentication updates are applied automatically across Windows, macOS, and Linux, risk-ranked and reported, independently of your RMM.
Lavawall® monitors releases and CVEs for SafeNet Authentication through public information and proprietary statistical analysis, and can patch it automatically across your fleet.