First published: Thu Jan 30 2014(Updated: )
I discovered (aside <a class="bz_bug_link bz_status_CLOSED bz_closed bz_public " title="CLOSED ERRATA - CVE-2014-0037 zarafa: unauthenticated denial of service flaw" href="show_bug.cgi?id=1056767">bug #1056767</a>) another flaw in Zarafa that could allow a remote unauthenticated attacker to crash the zarafa-server daemon, preventing access to any other legitimate Zarafa users. The issue affects all Zarafa versions from at least Zarafa 6.20.0 (maybe even from at least Zarafa 5.00) up to (including) Zarafa 7.1.8 final. Please note that I was not able to crash the zarafa-server daemon using official upstream Zarafa binary packages just all community builds from the source code such as shipped in Fedora. This different behaviour might be caused that upstream uses different built-time flags or other system libraries and headers. Once the zarafa-server process crashes with a backtrace (and even all other Zarafa related daemons are still running) there is no Zarafa functionality till zarafa-server daemon is started again. The zarafa-server process provides the MAPI in SOAP service required by all other Zarafa related components as shown: <a href="http://doc.zarafa.com/trunk/Administrator_Manual/en-US/html/_architecture.html">http://doc.zarafa.com/trunk/Administrator_Manual/en-US/html/_architecture.html</a>
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Zarafa Zarafa | <=6.20 | |
Zarafa Zarafa | =5.00 | |
Zarafa Zarafa | =5.01 | |
Zarafa Zarafa | =5.02 | |
Zarafa Zarafa | =5.10 | |
Zarafa Zarafa | =5.11 | |
Zarafa Zarafa | =5.20 | |
Zarafa Zarafa | =5.22 | |
Zarafa Zarafa | =6.00 | |
Zarafa Zarafa | =6.01 | |
Zarafa Zarafa | =6.02 | |
Zarafa Zarafa | =6.03 | |
Zarafa Zarafa | =6.10 | |
Zarafa Zarafa | =6.11 | |
Zarafa Zarafa | =7.1.8 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.