Unscored severity · published Oct 30, 2001
CVE-2001-0713
Sendmail before 8.12.1 does not properly drop privileges when the -C option is used to load custom configuration files, which allows local users to gain privileges via malformed…
–
CVSS
0.3%
EPSS
No
On KEV
Description
Sendmail before 8.12.1 does not properly drop privileges when the -C option is used to load custom configuration files, which allows local users to gain privileges via malformed arguments in the configuration file whose names contain characters with the high bit set, such as (1) macro names that are one character long, (2) a variable setting which is processed by the setoption function, or (3) a Modifiers setting which is processed by the getmodifiers function.
Exploitation
Is it being used?
Exploit prediction (EPSS)0.3% · higher than 26% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
SE
Sendmail · Sendmail
through 8.12.1 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2001-0713
CVE.org
https://www.cve.org/CVERecord?id=CVE-2001-0713
Vendor Advisory
http://razor.bindview.com/publish/advisories/adv_sm812.html
www.iss.net
http://www.iss.net/security_center/static/7192.php
www.securityfocus.com
http://www.securityfocus.com/bid/3377
More from Sendmail
7.5
CVE-2006-4434
Use-after-free vulnerability in Sendmail before 8.13.8 allows remote attackers to cause a denial of service (crash) via a long "header line", which causes a previously freed…
7.4
CVE-2021-3618
ALPACA is an application layer protocol content confusion attack, exploiting TLS servers implementing different protocols but using compatible certificates, such as multi-domain…
5.3
CVE-2023-51765
sendmail through 8.17.2 allows SMTP smuggling in certain configurations
–
CVE-2014-3956
The sm_close_on_exec function in conf.c in sendmail before 8.14.9 has arguments in the wrong order, and consequently skips setting expected FD_CLOEXEC flags, which allows local…
–
CVE-2009-4565
sendmail before 8.14.4 does not properly handle a '\0' character in a Common Name (CN) field of an X.509 certificate, which (1) allows man-in-the-middle attackers to spoof…
