First published: Thu May 19 2011(Updated: )
Dovecot has released version 1.2.17 [1] and 2.0.13 [2] to address a potential crash, and possibly mailbox corruption, when dovecot parsed header names that contained NUL characters. This was due to a pointer possibly pointing past allocated memory. An upstream patch [3] is available. [1] <a href="http://dovecot.org/pipermail/dovecot/2011-May/059086.html">http://dovecot.org/pipermail/dovecot/2011-May/059086.html</a> [2] <a href="http://dovecot.org/pipermail/dovecot/2011-May/059085.html">http://dovecot.org/pipermail/dovecot/2011-May/059085.html</a> [3] <a href="http://hg.dovecot.org/dovecot-1.1/rev/3698dfe0f21c">http://hg.dovecot.org/dovecot-1.1/rev/3698dfe0f21c</a>
Affected Software | Affected Version | How to fix |
---|---|---|
Dovecot | >=1.2.17<=2.0.13 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
REDHAT-BUG-706286 is considered a critical vulnerability due to its potential to cause crashes and mailbox corruption.
To fix REDHAT-BUG-706286, update Dovecot to version 1.2.17 or 2.0.13 or later.
The affected products of REDHAT-BUG-706286 include Dovecot versions from 1.2.17 to 2.0.13.
REDHAT-BUG-706286 is caused by a pointer potentially pointing past allocated memory when Dovecot parses header names with NUL characters.
Yes, an upstream patch is available to address the vulnerability described in REDHAT-BUG-706286.