CVE-2002-1293
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 Microsoft Java implementation, as used in Internet Explorer, provides a public load0() method for the CabCracker class (com.ms.vm.loader.CabCracker), which allows remote attackers to bypass the security checks that are performed by the load() method.
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 · moderate confidenceThe Microsoft Java implementation (com.ms.vm.loader.CabCracker class) in Internet Explorer contains a public load0() method that bypasses security checks performed by the load() method, allowing remote attackers to bypass Java sandbox restrictions.
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 data= 1.1CVSS 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 Java Virtual Machine is installedOpen Windows Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Java VM, or look for msjava.dll in system directories (System32 or Windows\System).Affected if The registry key exists or msjava.dll is present on the system.
-
Determine the Microsoft Java VM versionIn the same registry location (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Java VM), look for a Version value. Alternatively, right-click msjava.dll and select Properties > Version tab.Affected if The version is 1.1.x (specifically 1.1).
-
Verify the CabCracker class existsSearch for the file CabCracker.class or com/ms/vm/loader/CabCracker.class within the Microsoft Java VM installation directory or JAR files in the Java VM path.Affected if The CabCracker class file is found in the Microsoft Java VM installation.
-
Check if Java is enabled in Internet ExplorerOpen Internet Explorer > Tools > Internet Options > Security > Custom Level. Scroll to 'Java permissions' or 'Script ActiveX controls marked safe for scripting'. Also check 'Microsoft VM' section in Tools > Internet Options > Advanced.Affected if Java is enabled (not disabled) in IE security settings.
-
Confirm the vulnerable CabCracker.load0() method is presentUse a Java decompiler or class file viewer to examine the CabCracker.class file. Verify that a public method named 'load0()' exists that lacks the security checks present in the load() method.Affected if The load0() method exists as a public method without security checks.
The system is affected if Microsoft Java Virtual Machine version 1.1 is installed with the CabCracker class present and Java is enabled in Internet Explorer, allowing the insecure load0() method to be invoked.
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 dataDisable Java in Internet Explorer or remove the Microsoft Java Virtual Machine from affected systems, as Microsoft no longer provides patches for this legacy component.
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-1293 — 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-1293 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