LiveActive security incident?Get immediate response
CVE Record

CVE-2000-0319: mail.local in Sendmail 8.10.x does not properly identify the .\n string which identifies the end of message...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

A flaw in Sendmail 8.10.x's mail.local delivery program lets a remote sender crash mail delivery or corrupt user mailboxes by sending a specially crafted email line. The impact is disruption of email service and potential loss of stored mail, not data theft. It is a legacy issue from 2000 that only matters if very old Sendmail versions still run somewhere in the estate. Very limited in 2026. Exposure requires an internet-reachable mail host still running Sendmail 8.10.x with mail.local as the local delivery agent. Modern mail environments (Postfix, Exchange, cloud email, or supported Sendmail branches) are not affected. Legacy Unix systems, air-gapped labs, or unmanaged appliances embedding old Sendmail are the realistic residual exposure. Low priority. Treat as legacy hygiene: confirm no Sendmail 8.10.x is still in production, then close. Only escalate if inventory surfaces an unpatched legacy mail host handling business email, in which case retire or upgrade it as part of normal lifecycle work. Mitigation focus: Upgrade any Sendmail 8.10.x instance to a currently supported Sendmail release or a supported MTA.; Replace mail.local with a modern local delivery agent (for example, procmail or maildrop) where feasible.; Restrict inbound SMTP to trusted relays and enforce line-length limits at the perimeter mail gateway..

Prepared

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-2000-0319 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
1Source 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.