Skip to content
Fencer Vulns
medium 4.6

CVE-2001-0653 json

Sendmail 8.10.0 through 8.11.5, and 8.12.0 beta, allows local users to modify process memory and possibly gain privileges via a large value…

published 2001-09-20 25 y ago modified 2026-06-16 4 mo ago also EUVD-2001-0639

cvss
4.6
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 67%
public exploits
4
Exploit-DB

Summary

Sendmail 8.10.0 through 8.11.5, and 8.12.0 beta, allows local users to modify process memory and possibly gain privileges via a large value in the 'category' part of debugger (-d) command line arguments, which is interpreted as a negative number.

Patch / fix

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2001-0653 updated

security flaw

  • Red Hat Linux 5.2 Red Hat Linux 6.2 Red Hat Linux 7.0 Red Hat Linux 7.1
    fixed: vendor fix RHSA-2001:106

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. First public exploit (EDB-21063)
  2. Published

Exploit prediction

1.18% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • EDB-21063 Sendmail 8.11/8.12 Debugger - Arbitrary Code Execution (4) local, 2001-08-17
  • EDB-21062 Sendmail 8.11/8.12 Debugger - Arbitrary Code Execution (3) local, 2001-08-17
  • EDB-21061 Sendmail 8.11/8.12 Debugger - Arbitrary Code Execution (2) local, 2001-08-17
  • EDB-21060 Sendmail 8.11/8.12 Debugger - Arbitrary Code Execution (1) local, 2001-08-17
  • securityfocus.com http://www.securityfocus.com/bid/3163 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 4.6 AV:L/AC:L/Au:N/C:P/I:P/A:P

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.