3 ms·
> I've heard maybe Daniel J. Bernstein can DJB simply redefines his unsafe code as safe[0] and asserts that you're Using It Wrong: -- In May 2005, Georgi Gun
by masklinn 6y ago
> I've heard maybe Daniel J. Bernstein can
DJB simply redefines his unsafe code as safe[0] and asserts that you're Using It Wrong:
--
In May 2005, Georgi Guninski published "64 bit qmail fun", three
vulnerabilities in qmail (CVE-2005-1513, CVE-2005-1514, CVE-2005-1515): http://www.guninski.com/where_do_you_want_billg_to_go_today_4.html http://www.guninski.com/where_do_you_want_billg_to_go_today_...
Surprisingly, we re-discovered these vulnerabilities during a recent
qmail audit; they have never been fixed because, as stated by qmail's
author Daniel J. Bernstein (in https://cr.yp.to/qmail/guarantee.html https://cr.yp.to/qmail/guarantee.html):
> This claim is denied. Nobody gives gigabytes of memory to each
qmail-smtpd process, so there is no problem with qmail's assumption
that allocated array lengths fit comfortably into 32 bits.
Indeed, the memory consumption of each qmail-smtpd process is severely
limited by default (by qmail-smtpd's startup script); for example, on
Debian 10 (the latest stable release), it is limited to roughly 7MB.
Unfortunately, we discovered that these vulnerabilities also affect
qmail-local, which is reachable remotely and is not memory-limited by
default (we investigated many qmail packages, and all of them limit
qmail-smtpd's memory, but none of them limits qmail-local's memory).
As a proof of concept, we developed a reliable, local and remote exploit
against Debian's qmail package in its default configuration. This proof
of concept requires 4GB of disk space and 8GB of memory, and allows an
attacker to execute arbitrary shell commands as any user, except root
(and a few system users who do not own their home directory). We will
publish our proof-of-concept exploit in the near future.
About our new discovery, Daniel J. Bernstein issues the following
statement:
> https://cr.yp.to/qmail/guarantee.html https://cr.yp.to/qmail/guarantee.html has for many years mentioned
qmail's assumption that allocated array lengths fit comfortably into
32 bits. I run each qmail service under softlimit -m12345678, and I
recommend the same for other installations.
--
[0] https://www.openwall.com/lists/oss-security/2020/05/19/8 https://www.openwall.com/lists/oss-security/2020/05/19/8
PS: HN's markup keeps sucking and making comments unreadable
- knorker 6y agoIn other words the instructions on how to run qmail without security holes were clearly displayed in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying ‘Beware of the Leopard.
- cratermoon 6y ago"Nobody gives gigabytes of memory to each qmail-smtpd process"? ----- QUESTION: "I read in a newspaper that in l981 you said '640K of memory should be enough for anybody.' What did you mean when you said this?" ANSWER: "I've said some stupid things and some wrong things, but not that. No one involved in computers would ever say that a certain amount of memory is enough for all time." https://www.wired.com/1997/01/did-gates-really-say-640k-is-enough-for-anyone/ https://www.wired.com/1997/01/did-gates-really-say-640k-is-e... ----- If I were a cynical programmer I might think DJB just doesn't want to hand over a $500 check.