Idrix develops encryption and disk-protection software, with its vulnerability profile centered on VeraCrypt and related products that handle sensitive cryptographic operations and memory-resident key material. The observed weakness classes—including improper memory-buffer restrictions and untrusted search paths—reflect the low-level access and input-handling demands of full-disk encryption tools. Current severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Idrix over time
Signals from CVEs in this vendor scope (5 CVEs).
5 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2015-7358HIGH 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 sym | Oct 3, 2017 | 7.8 | 30 | NO | YES |
CVE-2019-19501HIGH VeraCrypt 1.24 allows Local Privilege Escalation during execution of VeraCryptExpander.exe. | Dec 13, 2019 | 7.8 | 22 | NO | NO |
CVE-2016-1281HIGH Untrusted search path vulnerability in the installer for TrueCrypt 7.2 and 7.1a, VeraCrypt before 1.17-BETA, and possibly other products allows local users to execute arbitrary cod | Jan 23, 2017 | 7.8 | 21 | NO | NO |
CVE-2015-7359HIGH 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 | Oct 3, 2017 | 7.8 | 20 | NO | NO |
IDRIX, Truecrypt Veracrypt, Truecrypt Prior to 1.23-Hotfix-1 (Veracrypt), all versions (Truecrypt) is affected by: Buffer Overflow. The impact is: Minor information disclosure of k | Jul 23, 2019 | 3.3 | 14 | NO | NO |
Signals from CVEs in this vendor scope (5 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Idrix.
Media articles that mention a CVE ID that affects a product developed by Idrix — matched by CVE ID, not by vendor name.