CVE-2002-1325
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMicrosoft Virtual Machine (VM) build 5.0.3805 and earlier allows remote attackers to determine a local user's username via a Java applet that accesses the user.dir system property, aka "User.dir Exposure Vulnerability."
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMicrosoft Virtual Machine (VM) build 5.0.3805 and earlier contains a vulnerability where a malicious Java applet can access the user.dir system property, which typically reveals the local user's username since it contains the path to the user's home directory.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsall versionsall versionsall versionsall versionsall versions= 4.0all versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if Microsoft VM is installedLook for the Microsoft Java Virtual Machine installation on the system. On affected Windows versions, check the Java runtime installation directory or the Windows system components for Microsoft VM files (typically found in Windows\Java or system directories).Affected if Microsoft VM is present on the system
-
Identify the Microsoft VM build versionLocate the Microsoft VM executable or DLL file (such as java.exe, javaw.exe, or msjava.dll) and check its version property. The build number is typically displayed as 5.0.xxxx where xxxx is the build identifier.Affected if The build number is 5.0.3805 or lower
-
Verify the Windows version is affectedCheck the operating system version. Open Command Prompt and run 'winver' or check System Properties to confirm the Windows version.Affected if Running Windows 2000, Windows 95, Windows 98, Windows 98se, Windows Me, Windows NT 4.0, or Windows XP
-
Confirm Java applet execution is possibleCheck browser settings or Java control panel to determine if Java applets can be executed. This vulnerability requires a browser to run an untrusted Java applet.Affected if Browsers or Java environments are configured to allow execution of untrusted Java applets
The system is affected if Microsoft VM build 5.0.3805 or earlier is installed on a supported Windows version (2000, 95, 98, 98se, Me, NT 4.0, XP) and the browser can execute Java applets.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRemove or disable Microsoft VM and ensure browsers are configured to block untrusted Java applets, or migrate to a supported Java runtime environment.
- Consultation4.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,912.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-1325 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2002-1325 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data