Re: Buffer overflow in the StringQuotedWord() function

William Bader <[email protected]> Sat, 21 Dec 2019 11:59:47 +0000
Newsgroups gmane.comp.type-setting.lout
Message-ID <AM0PR04MB60509D06A3FED1CAAF0A0A30C42C0@AM0PR04MB6050.eurprd04.prod.outlook.com>
Is anyone still maintaining lout?

I have attached patches that fix some graph issues and that add some features.

Is there a consensus how to fix the two overflows that you reported?
The easiest way is probably truncating the buffer and showing a warning, but that might lose text.
Other places in lout might have the same buffer limit, so allocating and passing a larger buffer would take some analysis to ensure that it wouldn't cause a buffer overflow somewhere else.

Regards, William


________________________________
From: Lout-users <[email protected]> on behalf of Frederic Cambus <[email protected]>
Sent: Saturday, December 21, 2019 5:27 AM
To: [email protected] <[email protected]>
Subject: Re: Buffer overflow in the StringQuotedWord() function

On Fri, Dec 20, 2019 at 07:12:14PM +0100, Frederic Cambus wrote:

> While fuzzing lout 3.40 with Honggfuzz, I found a buffer overflow in
> the StringQuotedWord() function, in z39.c.

This issue has been assigned CVE-2019-19917.

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19917
lout-3.40.pat.gz (application/gzip, 12 KB) - not displayed