CVE-2000-0319: Medium severity Eric Allman Sendmail vulnerability

Published Apr 23, 2000
·
Updated

mail.local in Sendmail 8.10.x does not properly identify the .\n string which identifies the end of message text, which allows a remote attacker to cause a denial of service or corrupt mailboxes via a message line that is 2047 characters long and ends in .\n.

Affected Software

19 affected components
Eric Allman Sendmail=5.58
Eric Allman Sendmail=5.59
Eric Allman Sendmail=8.6.x
Eric Allman Sendmail=8.7.1
Eric Allman Sendmail=8.7.2
Eric Allman Sendmail=8.7.3
Eric Allman Sendmail=8.7.4
Eric Allman Sendmail=8.7.5
Eric Allman Sendmail=8.7.6
Eric Allman Sendmail=8.7.x
Eric Allman Sendmail=8.8
Eric Allman Sendmail=8.8.1
Eric Allman Sendmail=8.8.2
Eric Allman Sendmail=8.8.3
Eric Allman Sendmail=8.8.4
Eric Allman Sendmail=8.8.5
Eric Allman Sendmail=8.8.x
Eric Allman Sendmail=8.9.1
Eric Allman Sendmail=8.9.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Remove

    Remove sendmail/mail.local from your environment.

    If mail.local is not required, uninstall or disable the mail.local delivery agent to eliminate the vulnerable component (prevents mail.local from processing incoming messages).

  2. Compensating control

    Restrict remote access to the Sendmail SMTP service (TCP port 25) at the network perimeter or host firewall so only trusted systems can submit mail, reducing exposure to remote attackers.

  3. Compensating control

    Deploy or configure a mail gateway/proxy or SMTP filter to reject or normalize incoming message lines that are 2047 characters long (or otherwise unusually long) and to correctly enforce end-of-message markers (e.g., the ".\n" terminator) before passing messages to Sendmail/mail.local.

Event History

Apr 23, 2000
CVE Published
04:00 AM
Data Sourced
via NVD·04:00 AM
RemedyDescriptionSeverityAffected Software
Oct 13, 2000
CVE Published
via MITRE·08:00 AM
Data Sourced
via MITRE·08:00 AM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2000-0319?

The severity of CVE-2000-0319 is considered moderate due to the possibility of denial of service or mailbox corruption.

2

How do I fix CVE-2000-0319?

To fix CVE-2000-0319, upgrade to a version of Sendmail that is not affected, such as 8.10.0 or later.

3

What versions of Sendmail are affected by CVE-2000-0319?

CVE-2000-0319 affects Sendmail versions 8.6.x to 8.9.x and some 8.7.x versions.

4

What type of attack does CVE-2000-0319 enable?

CVE-2000-0319 enables a remote attacker to cause a denial of service or corrupt mailboxes.

5

Is CVE-2000-0319 still a risk for current systems?

CVE-2000-0319 is a historical vulnerability, but systems still using old affected versions of Sendmail remain at risk.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203