Patch & vulnerability status
TrueCrypt 7.1.1
Latest tracked version 7.1.1. Release status, tracked CVEs, and automated cross-platform patching for TrueCrypt.
| Platform | Latest version | CVEs tracked | Last checked |
|---|---|---|---|
| Windows | 7.1.1 | 4 | 2024-07-02 |
Known vulnerabilities (CVEs) in TrueCrypt
Lavawall tracks 4 published CVEs affecting TrueCrypt, and deploys the versions that fix them automatically across your fleet.
| CVE | Published | Severity | Details | Vector |
|---|---|---|---|---|
| CVE-2015-7359 | 2017-10-03 01:29:01 | MEDIUM (5) | The (1) IsVolumeAccessibleByCurrentUser and (2) MountDevice methods in Ntdriver.c in TrueCrypt 7.0, VeraCrypt before 1.15, and CipherShed, when running on Windows, do not check the impersonation level of impersonation tokens, which allows local users to impersonate a user at SecurityIdentify level and gain access to other users' mounted encrypted volumes. | LOCAL |
| CVE-2015-7358 | 2017-10-03 01:29:01 | HIGH (7) | The IsDriveLetterAvailable method in Driver/Ntdriver.c in TrueCrypt 7.0, VeraCrypt before 1.15, and CipherShed, when running on Windows, does not properly validate drive letter symbolic links, which allows local users to mount an encrypted volume over an existing drive letter and gain privileges via an entry in the /GLOBAL?? directory. | LOCAL |
| CVE-2014-2885 | 2018-03-19 21:29:01 | LOW (4) | Multiple integer overflows in TrueCrypt 7.1a allow local users to (1) obtain sensitive information via vectors involving a crafted item->OriginalLength value in the MainThreadProc function in EncryptedIoQueue.c or (2) cause a denial of service (memory consumption) via vectors involving large StartingOffset and Length values in the ProcessVolumeDeviceControlIrp function in Ntdriver.c. | LOCAL |
| CVE-2014-2884 | 2018-03-19 21:29:01 | LOW (2) | The ProcessVolumeDeviceControlIrp function in Ntdriver.c in TrueCrypt 7.1a allows local users to bypass access restrictions and obtain sensitive information about arbitrary files via a (1) TC_IOCTL_OPEN_TEST or (2) TC_IOCTL_GET_SYSTEM_DRIVE_CONFIG IOCTL call. | LOCAL |
Why keeping TrueCrypt 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 TrueCrypt 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 TrueCrypt
Lavawall® watches TrueCrypt 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 TrueCrypt, one policy to bring them current, and timestamped evidence for audits.
Frequently asked questions
Lavawall tracks TrueCrypt at version 7.1.1 (last checked 2024-07-02). New releases are monitored continuously and can be deployed automatically across your fleet.
Lavawall tracks 4 CVEs for TrueCrypt and remediates them automatically as part of patching.
Deploy the Lavawall® agent and TrueCrypt updates are applied automatically across Windows, macOS, and Linux, risk-ranked and reported, independently of your RMM.
Lavawall® monitors releases and CVEs for TrueCrypt through public information and proprietary statistical analysis, and can patch it automatically across your fleet.