CVE-2002-1260
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 · uneditedThe Java Database Connectivity (JDBC) APIs in Microsoft Virtual Machine (VM) 5.0.3805 and earlier allow remote attackers to bypass security checks and access database contents via an untrusted Java applet.
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 confidenceThe Microsoft Virtual Machine (VM) 5.0.3805 and earlier contains a flaw in its Java Database Connectivity (JDBC) implementation where untrusted Java applets can bypass sandbox security restrictions and directly access database contents through JDBC APIs, allowing confidential data exposure without proper authentication.
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
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 installedSearch for msjava.dll or jview.exe in the Windows\System32 directory, or check the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Java VMAffected if Either file exists or the registry key is present
-
Determine Microsoft VM versionRight-click on msjava.dll or jview.exe in Windows\System32, select Properties, and view the Version tab to find the file versionAffected if File version is 5.0.3805 or earlier
-
Verify JDBC component presenceLook for jdbc*.dll files in the Windows\System32 directory or check if the JDBC driver is listed in the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Java VM\InstalledClassPathAffected if JDBC DLL files exist or JDBC is registered as an installed class path
-
Confirm Windows version is in affected listRun 'winver' or check System Properties to identify the Windows versionAffected if Running Windows 2000, Windows 95, Windows 98, Windows 98se, Windows Me, Windows NT 4.0, or Windows XP
If Microsoft VM version 5.0.3805 or earlier is installed on an affected Windows version and JDBC components are present, the environment is vulnerable to the sandbox bypass.
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 dataSince Microsoft VM is deprecated and no longer supported, the recommended remediation is to migrate to a supported Java runtime environment (such as Oracle Java or OpenJDK) and review database access controls to ensure proper authentication is enforced regardless of client-side restrictions.
- Consultation8.0 h
- Implementation40.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $20,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-1260 — 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-1260 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