Security readout for executives and security teams
Plain-English summary
This is a legacy clipboard privacy issue. A document containing ActiveX content could use Microsoft Forms 2.0, included with Visual Basic for Applications 5.0, to read text from a user's clipboard when the document is accessed.
Executive priority
This should be treated as a legacy data-exposure risk. It is not supported by the bundle as an active emergency, but it deserves attention where old ActiveX document workflows remain enabled.
Technical view
The CVE describes unauthorized clipboard text access through the Forms 2.0 ActiveX control in documents with ActiveX content. The provided record does not include CVSS, CWE, affected version detail, or specific remediation text beyond the Microsoft MS99-001 advisory reference.
Likely exposure
Exposure is most likely in legacy environments that still process documents with ActiveX content and support Forms 2.0 or VBA 5.0-era components. The provided affected-product data is listed as n/a, so exact product scope is incomplete.
Exploitation context
The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. The described condition requires a user to access a document with ActiveX content while clipboard text is available to be read.
Researcher notes
Evidence is sparse. The core issue is clipboard text disclosure through Forms 2.0 ActiveX content. Do not infer affected products, modern Office impact, exploit availability, or patch status beyond the CVE record and MS99-001 reference.
Mitigation direction
- Review Microsoft MS99-001 for vendor remediation guidance.
- Restrict or disable ActiveX content in documents where feasible.
- Inventory legacy VBA 5.0 or Forms 2.0 dependencies.
- Limit handling of untrusted documents in legacy document viewers.
- Educate users not to open unexpected ActiveX-enabled documents.
Validation and detection
- Check whether ActiveX document content is permitted in the environment.
- Identify systems supporting Forms 2.0 or VBA 5.0-era components.
- Review endpoint controls for blocked or allowed ActiveX execution.
- Confirm vendor guidance from MS99-001 was applied where relevant.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CVE-1999-0384 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
- MS99-001CVE reference · vendor-advisory, x_refsource_MS
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.