Re: [exim] bad memory reference; pool not found, at gstring…

Top Page
Delete this message
Reply to this message
Author: Jeremy Harris
Date:  
To: exim-users
Subject: Re: [exim] bad memory reference; pool not found, at gstring_grow 1124
On 20/12/2022 17:12, Andreas Metzler via Exim-users wrote:
> Is there a security impact of the bug?


Nope. Logging only... and only if you've written your
config to try and save an 8 kB (with the release size of
log buffer) log message.

I guess, if you have, an attacker could induce a lot of
process terminations. Most systems won't have setuid-coredumps
enabled, so little issue there.
--
Cheers,
Jeremy