Analyst readout for executives and security teams
Plain-English summary
This is a legacy Microsoft Virtual Machine issue where a malicious Java applet could cause Windows to load and run a DLL. Business risk is mainly in old environments that still allow Microsoft VM Java applets. The source bundle does not show active exploitation.
Executive priority
Treat as high priority only if legacy Microsoft VM remains in use. For most modern fleets, priority is discovery and retirement planning rather than emergency response, because active exploitation is not shown in the supplied sources.
Technical view
The JDBC classes in Microsoft VM up to and including 5.0.3805 can be abused through com.ms.jdbc.odbc.JdbcOdbc constructor handling. A remote attacker could use a Java applet and a null-terminated DLL name to trigger DLL loading and execution.
Likely exposure
Likely exposure is limited to legacy Windows/browser stacks retaining Microsoft VM version 5.0.3805 or earlier with Java applet execution reachable. Modern environments are unlikely to be exposed, but legacy business applications may preserve this runtime.
Exploitation context
The CVE describes remote attack through a Java applet. The provided data marks CISA KEV as false and includes no cited evidence of active exploitation. Public vulnerability database and advisory references exist, but exploit availability is not established here.
Researcher notes
The affected product metadata is incomplete, but the description identifies Microsoft VM through version 5.0.3805. Analysis should stay tied to MS02-052, CERT VU#307306, and the applet-based JDBC DLL-loading behavior. No CVSS, CWE, or KEV evidence is provided.
Mitigation direction
- Inventory systems for Microsoft VM 5.0.3805 or earlier.
- Review Microsoft MS02-052 and apply vendor-recommended updates or workarounds.
- Disable legacy Java applet execution where it is not operationally required.
- Retire or isolate systems that require the affected Microsoft VM.
Validation and detection
- Confirm whether Microsoft VM is installed and identify its version.
- Check browsers and legacy apps for Java applet dependency.
- Verify MS02-052 guidance has been applied on affected hosts.
- Prioritize review of externally reachable or user-browsing systems.
Public sources used
Based on public source material and reviewed before publication.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Database behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2002-0866 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- msvm-jdbc-dll-execution(10133)CVE reference · vdb-entry, x_refsource_XF
- VU#307306CVE reference · third-party-advisory, x_refsource_CERT-VN
- MS02-052CVE reference · vendor-advisory, x_refsource_MS
- 5751CVE reference · vdb-entry, x_refsource_BID
- 20020923 Technical information about the vulnerabilities fixed by MS-02-52CVE reference · mailing-list, x_refsource_BUGTRAQ
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
