LiveActive security incident?Get immediate response
CVE Record

CVE-1999-0207: Remote attacker can execute commands through Majordomo using the Reply-To field and a "lists" command.

Remote attacker can execute commands through Majordomo using the Reply-To field and a "lists" command.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a very old flaw in Majordomo, a mailing list program from the 1990s. A remote sender could trick the software into running commands on the mail server by manipulating the email Reply-To field along with a "lists" request. It matters only if legacy Majordomo installations still exist.

Executive priority

Low priority for modern estates. Only relevant if legacy Majordomo mailing list servers remain in use; if so, plan retirement or isolation.

Technical view

CVE-1999-0207 describes a remote command execution in Majordomo where an attacker can influence command processing via the email Reply-To header when issuing a "lists" command. The bundle lists no CVSS, CWE, affected versions, or patches. Reference material is limited to the IBM X-Force entry and CVE metadata.

Likely exposure

Exposure is limited to environments still running vintage Majordomo mailing list software reachable via email. Modern organizations are unlikely to be affected, but legacy Unix mail infrastructure could still harbor vulnerable installs.

Exploitation context

The source bundle does not indicate KEV listing or confirmed active exploitation. The issue is described as a remote command execution against Majordomo triggered by a crafted Reply-To field combined with a "lists" command. No exploit details are provided here.

Researcher notes

Public bundle is sparse: no CVSS, CWE, affected version list, or patch reference. The XForce entry is the primary technical pointer. Treat as a historical remote command execution in Majordomo email processing; validate against archival vendor advisories before assigning severity.

Mitigation direction

  • Identify any Majordomo mailing list servers still in production or lab environments.
  • Retire or replace Majordomo with a supported mailing list manager.
  • If retention is required, isolate the host and restrict inbound mail sources.
  • Consult vendor or maintainer guidance for any available patched builds.

Validation and detection

  • Inventory mail infrastructure for any Majordomo processes or configuration files.
  • Review SMTP logs for unusual list-management traffic to legacy mailing list hosts.
  • Cross-check any discovered instances against archival Majordomo advisories.
  • Confirm decommissioning by verifying the service no longer accepts mail.
Prepared
Confidence
low
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CVE-1999-0207 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.