CVE-2015-7358 json
The IsDriveLetterAvailable method in Driver/Ntdriver.c in TrueCrypt 7.0, VeraCrypt before 1.15, and CipherShed, when running on Windows, do…
published 2017-10-02 9 y ago modified 2026-06-17 4 mo ago also EUVD-2015-7282
- cvss
- 7.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 68%
- public exploits
- 1
- Exploit-DB
Summary
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.
Timeline
- First public exploit (EDB-38403)
- Published
Exploit prediction
1.21% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-38403 TrueCrypt 7 / VeraCrypt 1.13 - Drive Letter Symbolic Link Creation Privilege Escalation local, 2015-10-05
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.8 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-264 Permissions, Privileges, and Access Controls
References
-
exploit-db.com
/exploits/38403/
exploit, third-party-advisory, vdb-entry
-
veracrypt.codeplex.com
/wikipage?title=Release%20Notes
release-notes, vendor-advisory
-
openwall.com
/lists/oss-security/2015/09/24/3
mailing-list, issue-tracking, third-party-advisory
-
packetstormsecurity.com
/files/133878/Truecrypt-7-Derived-Code-Windows-Drive-Letter-Symbolic-Link-Creation-Privilege-Escalation.html
third-party-advisory, vdb-entry
-
openwall.com
/lists/oss-security/2015/09/22/7
mailing-list, third-party-advisory
-
code.google.com
/p/google-security-research/issues/detail?id=538
third-party-advisory
Sources
- CVE List CVE-2015-7358
- NVD CVE-2015-7358
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.