Re: Fwd: report 2/3: unsafe handling of excessive IMAP message counts
"Kevin J. McCarthy" <[email protected]> Thu, 18 Jun 2026 08:16:43 +0800
| Newsgroups | gmane.mail.mutt.devel |
|---|---|
| Message-ID | <[email protected]> |
On Thu, Jun 18, 2026 at 08:09:10AM +0800, Kevin J. McCarthy wrote: >----- Forwarded message from Acts1631 <[email protected]> ----- >From: Acts1631 <[email protected]> >imap_alloc_msn_index() checks for maliciously large IMAP message sequence number counts before allocating idata->msn_index: > > if (msn_count >= (UINT_MAX / sizeof(HEADER *))) > { > mutt_error _("Integer overflow -- can't allocate memory."); > sleep(1); > mutt_exit(1); > } > >Calling mutt_exit(1) terminates the mutt process. A robust IMAP client should reject the mailbox/update and return an error to the caller instead of exiting the program. This is a NAK for me. I'm open for debate on this, but defifinitely not before 2.4.0. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEiXWpszqjeRA4XFMIre92hIAxa9oFAmozOOsACgkQre92hIAx a9ro/g/+KfwaZzTj0EsJ6Ja2rXc7C091Z0ncG9XORr+FOW8h7q0WI2ZRxKAJuC34 gKe0nvpb/Xb8WsbuLuO7u1KIDQCzeY+YioiN3ncHS3K0Jj5gSzQhF0aPuXgAOfmF TKoaFShUxx7dXWqsVaVYIM5XDHvJUdfIkg6P1gI9tv2cDqJmU5uNbXkOjfCk1IM9 B+FLrgak491Bb4+XAIYhv4Cic10ugNbfJUpHp3OoZMaxYVEze5CEbgilwHk54pMO h2EeqrsSepAA8oF9rC3amfv8tawK/HmuMt1f7Qnwidquw03A693RgeQ0I2Hvc75g v2g6ZNou9wkJu6QChDP+2VLhSXhw4sV7mDhtWmubL8INPCVOilqS4dpa3ab13qmv U9wiAvFm+kz2db+co17mAKaDnxffxfNW3o/UQndw7+sb3sJxIVYP1lUlh3wmB0OS YKWVmmVfHTAljdUu/DIqwvc+zD6HdXniQdDoc3WwCbG9DW8ZulWbCANxTs27s4zN WdK7UT7DZW5yseILLxT5D/DnvIzN5ETTtmXzNcvfjxjrmzfQYwqejJI7jpFzhODZ mRD5zDrnl8znKh9hct7e/m+xb3VzylDyhSo6JatgilRXGN/vUI3m18kM+/tBQa8e Xrko808YWTxco+NqoOKLKCanvTNuxd8Osmq6HA9D2k5kTeB1GCk= =Gs/B -----END PGP SIGNATURE-----