GMime parser bug

Albrecht Dreß <[email protected]> Fri, 07 Feb 2020 18:41:40 +0100

Newsgroups	gmane.comp.gnome.apps.balsa
Message-ID	<[email protected]>

Hi all,

using a different tool I wrote at work, I stumbled across a nasty bug in the GMime parser which can under adverse conditions lead to a loss of the beginning of message or message part content.  This bug also affects Balsa.

Basically, it occurs if the 2nd LF of the CR LF CR LF sequence terminating the headers of the message or a message part is the very first byte of a new 4k block (this actually happens quite frequently) *and* if the following body begins with text which somehow looks like a header (which is a lot less likely).

Unfortunately, this bug seems to be present in all GMime versions, including 2.6 (Balsa's master branch) and 3.2 (gmime3 branch).

For more details and POC messages see <https://github.com/jstedfast/gmime/issues/78>.

Hopefully, Jeff can fix this issue soon…

Best,
Albrecht.

_______________________________________________
balsa-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/balsa-list

signature.asc (application/pgp-signature, 488 B)