First published: Mon Jul 09 2018(Updated: )
Sophos SafeGuard Enterprise before 8.00.5, SafeGuard Easy before 7.00.3, and SafeGuard LAN Crypt before 3.95.2 are vulnerable to Local Privilege Escalation via IOCTL 0x80202014. By crafting an input buffer we can control the execution path to the point where the constant 0xFFFFFFF will be written to a user-controlled address. We can take advantage of this condition to modify the SEP_TOKEN_PRIVILEGES structure of the Token object belonging to the exploit process and grant SE_DEBUG_NAME privilege. This allows the exploit process to interact with higher privileged processes running as SYSTEM and execute code in their security context.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Sophos SafeGuard Easy Device Encryption Client | =6.00 | |
Sophos SafeGuard Easy Device Encryption Client | =6.10 | |
Sophos SafeGuard Easy Device Encryption Client | =7.00 | |
Sophos SafeGuard Enterprise Client | =5.60.3-vs-nfd | |
Sophos SafeGuard Enterprise Client | =6.00 | |
Sophos SafeGuard Enterprise Client | =6.00.1 | |
Sophos SafeGuard Enterprise Client | =6.10 | |
Sophos SafeGuard Enterprise Client | =7.00 | |
Sophos SafeGuard Enterprise Client | =8.00 | |
Sophos SafeGuard LanCrypt Client | =3.90.1-ts | |
Sophos SafeGuard LanCrypt Client | =3.90.2 | |
Sophos SafeGuard LanCrypt Client | =3.95.1 | |
Sophos SafeGuard LanCrypt Client | =3.95.1-ts |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2018-6855 is classified as a local privilege escalation vulnerability that poses significant risk for affected systems.
To fix CVE-2018-6855, upgrade your Sophos SafeGuard Enterprise, SafeGuard Easy, or SafeGuard LAN Crypt to the latest patched version.
CVE-2018-6855 affects Sophos SafeGuard Enterprise before 8.00.5, SafeGuard Easy before 7.00.3, and SafeGuard LAN Crypt before 3.95.2.
CVE-2018-6855 is associated with local privilege escalation attacks through crafted input buffers.
There are no specific workarounds recommended for CVE-2018-6855; updating to the latest version is the best mitigation.