CVE-1999-0207
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 · uneditedRemote attacker can execute commands through Majordomo using the Reply-To field and a "lists" command.
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 · moderate confidenceMajordomo mailing list software allows remote command execution through manipulation of the Reply-To email header when invoking the 'lists' command, enabling attackers to inject arbitrary shell commands via crafted email messages.
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.90= 1.91CVSS 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
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Identify if Majordomo is installedLook for the majordomo executable or configuration files in common locations such as /usr/local/majordomo, /var/lib/majordomo, or check for the majordomo alias in /etc/aliases or /etc/mail/aliasesAffected if Majordomo software is present on the system
-
Determine the installed Majordomo versionCheck the version file typically found in the Majordomo installation directory, or run 'majordomo -v' if available, or examine the contents of the majordomo script for version strings like '1.90' or '1.91'Affected if The version is 1.90 or 1.91 specifically
-
Verify the 'lists' command is email-accessibleCheck the mail aliases configuration (e.g., /etc/aliases or /etc/mail/aliases) for entries that pipe incoming email to the majordomo script for command processing, such as 'majordomo: "|/path/to/majordomo"' or 'owner-majordomo: ...'Affected if An alias routes email commands to Majordomo without sanitization
-
Confirm email header processing is enabledExamine the Majordomo configuration file (typically majordomo.cf) for settings that enable Reply-To header processing or command parsing from email messagesAffected if Configuration allows Reply-To headers from incoming email to be processed as commands
The system is affected if Majordomo versions 1.90 or 1.91 are installed and configured to accept email commands, allowing the 'lists' command to process Reply-To headers without sanitization.
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 dataApply available patches for Majordomo; as a defense-in-depth measure, implement email header validation and filtering at the mail server level to sanitize or reject malicious Reply-To headers before they reach the mailing list software.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-0207 — 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-1999-0207 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