CVE-2004-0838
Lexar Safe Guard for JumpDrive Secure 1.0 stores the password insecurely in memory using XOR...
Lexar Safe Guard for JumpDrive Secure 1.0 stores the password insecurely in memory using XOR encryption, which allows local users to read the password directly from the device and access the password protected part of the drive.
Exploit likelihood
What each source reports
NVD Score used
Lexar Safe Guard for JumpDrive Secure 1.0 stores the password insecurely in memory using XOR encryption, which allows local users to read the password directly from the device and access the password protected part of the drive.
- Record
CVE-2004-0838- CVSS 2.0
- 2.1 Low
AV:L/AC:L/Au:N/C:P/I:N/A:N - Updated
- 2026-11-02
CVE List No score
Lexar Safe Guard for JumpDrive Secure 1.0 stores the password insecurely in memory using XOR encryption, which allows local users to read the password directly from the device and access the password protected part of the drive.
- Record
CVE-2004-0838- Updated
- 2026-11-02
EUVDEUVD-2004-0836 No score
Lexar Safe Guard for JumpDrive Secure 1.0 stores the password insecurely in memory using XOR encryption, which allows local users to read the password directly from the device and access the password protected part of the drive.
- Record
EUVD-2004-0836- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-74rf-qhrr-fxrm No score
Lexar Safe Guard for JumpDrive Secure 1.0 stores the password insecurely in memory using XOR...
Lexar Safe Guard for JumpDrive Secure 1.0 stores the password insecurely in memory using XOR encryption, which allows local users to read the password directly from the device and access the password protected part of the drive.
- Record
GHSA-74rf-qhrr-fxrm- Updated
- 2026-11-02
Affected products
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2004-0838 is a low vulnerability (CVSS 2.1) in Lexar Jumpdrive Secure, published September 13, 2004. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.22%, the 13th percentile. No source names a fixed version.