Security readout for executives and security teams
Plain-English summary
CVE-1999-0365 describes a legacy metamail issue where unsafe mailcap handling could let specially crafted email content trigger remote command execution. The source bundle does not identify affected versions, severity, a patch, or active exploitation. Treat this as a legacy-exposure risk that matters mainly where metamail or related mailcap processing still exists.
Executive priority
Prioritize discovery over emergency response unless metamail is present in exposed mail workflows. If found, reduce or remove the legacy processing path because the stated impact is remote command execution.
Technical view
The CVE states that metamail fails to quote shell metacharacters in a mailcap entry, allowing remote command execution. Published affected product metadata is incomplete in the bundle, and no CVSS, CWE, fixed version, or KEV listing is provided. Validation should focus on whether metamail and risky mailcap entries remain in mail-processing paths.
Likely exposure
Likely exposure is limited to legacy systems that still install or invoke metamail for MIME or mailcap-based content handling. The bundle lists vendor, product, and versions as unavailable.
Exploitation context
The bundle supports remote command execution as the impact, but it does not provide exploit status, exploitation prevalence, or KEV evidence. Do not assume active exploitation from these sources.
Researcher notes
Evidence is sparse: the CVE description names the flaw class, but affected versions, patch status, CVSS, CWE, and exploit observations are absent. Analysis should avoid expanding scope beyond metamail and mailcap handling.
Mitigation direction
- Inventory systems for metamail installation or dependency use.
- Remove metamail where it is not operationally required.
- Review mailcap entries for unsafe shell metacharacter handling.
- Check operating-system or vendor guidance for fixed packages or supported replacements.
- Restrict untrusted MIME processing on systems that must retain legacy handlers.
Validation and detection
- Confirm whether metamail exists on mail clients, gateways, or legacy servers.
- Identify workflows that pass untrusted mail content to mailcap handlers.
- Review mailcap configuration ownership and change history.
- Check vendor package metadata for maintenance status and available updates.
- Document compensating controls for any retained legacy processing path.
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-0365 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
- https://exchange.xforce.ibmcloud.com/vulnerabilities/CVE-1999-0365CVE reference · x_refsource_MISC
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.