CVE-2002-1290
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, allows remote attackers to read and modify the contents of the Clipboard via an applet that accesses the (1) ClipBoardGetText and (2) ClipBoardSetText methods of the INativeServices class.
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 Java implementation in Internet Explorer contains a vulnerability where a malicious applet can access clipboard contents through the INativeServices class methods (ClipBoardGetText and ClipBoardSetText). This allows remote attackers to read or modify the clipboard without user consent.
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
- None
AV:N/AC:L/Au:N/C:P/I:P/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.
-
Verify Microsoft Java VM installationCheck for Microsoft Java Virtual Machine presence in system: Open Windows Registry editor and look for key HKLM\SOFTWARE\Microsoft\Java VM, or check C:\Windows\System32\msjava.dll existenceAffected if Microsoft Java VM is installed on the system
-
Confirm Microsoft Java VM versionCheck the version of msjava.dll or query the Microsoft Java VM through Java version command: 'java -version' from Microsoft JVM, or view file properties of msjava.dllAffected if Version is exactly 1.1.x (specifically 1.1)
-
Verify Internet Explorer Java plugin statusIn Internet Explorer, go to Tools > Internet Options > Security > Custom Level > Script ActiveX controls marked safe for scripting - check if Java permissions are enabled, or check IE plugin list for Microsoft JVMAffected if Internet Explorer has Microsoft Java VM enabled as an ActiveX/plugin option
-
Confirm INativeServices class accessibilityThe vulnerability requires that Java applets can execute and access the native interface. Check if Microsoft VM is set to allow applets to run in IE without strict security prompts, or examine msjava.dll exports for INativeServices interfaceAffected if Microsoft Java VM 1.1 is active in IE and allows unsigned applet execution with native method access
A system is affected only if Microsoft Java Virtual Machine version 1.1 is installed and enabled in Internet Explorer, allowing Java applets to access the INativeServices class methods.
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 or remove the Microsoft Java VM from Internet Explorer, or use an alternative browser that does not support the vulnerable Java implementation. This is a legacy 2002 vulnerability affecting obsolete systems.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-1290 — 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-1290 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