CVE-2008-3899: Infoleak
First published: Wed Sep 03 2008(Updated: )
TrueCrypt 5.0 stores pre-boot authentication passwords in the BIOS Keyboard buffer and does not clear this buffer before and after use, which allows local users to obtain sensitive information by reading the physical memory locations associated with this buffer. NOTE: the researcher mentions a response from the vendor denying the vulnerability.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| TrueCrypt | =5.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2008-3899?
CVE-2008-3899 is considered a high-severity vulnerability due to the potential exposure of sensitive authentication information.
How can I mitigate the effects of CVE-2008-3899?
To mitigate CVE-2008-3899, it is recommended to upgrade to a version of TrueCrypt that does not store passwords in the BIOS keyboard buffer.
Who is affected by CVE-2008-3899?
Users of TrueCrypt version 5.0 are directly affected by CVE-2008-3899.
What information can be compromised due to CVE-2008-3899?
CVE-2008-3899 allows local users to potentially retrieve pre-boot authentication passwords stored in physical memory.
Is TrueCrypt still a viable encryption solution given CVE-2008-3899?
Given the vulnerabilities like CVE-2008-3899, it is advisable to consider alternative encryption solutions as TrueCrypt is no longer maintained.
- agent/references
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/weakness
- agent/last-modified-date
- agent/author
- agent/first-publish-date
- agent/event
- agent/description
- agent/source
- agent/tags
- agent/softwarecombine
- collector/nvd-historical
- agent/software-canonical-lookup-request
- collector/nvd-index
- vendor/truecrypt foundation
- canonical/truecrypt
- version/truecrypt/5.0