Red Hat Bugzilla – Full Text Bug Listing
|Summary:||CVE-2012-3482 fetchmail: DoS (crash) in the base64 decoder upon server NTLM protocol exchange abort right after the initial request|
|Product:||[Other] Security Response||Reporter:||Jan Lieskovsky <jlieskov>|
|Component:||vulnerability||Assignee:||Red Hat Product Security <security-response-team>|
|Status:||NEW ---||QA Contact:|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:||847989|
Description Jan Lieskovsky 2012-08-14 05:33:48 EDT
A denial of service flaw was found in the way Fetchmail, a remote mail retrieval and forwarding utility, performed base64 decoding of certain NTLM server responses. Upon sending the NTLM authentication request, Fetchmail did not check if the received response was actually part of NTLM protocol exchange, or server-side error message and session abort. A rogue NTML server could use this flaw to cause fetchmail executable crash. Upstream patches:  http://gitorious.org/fetchmail/fetchmail/commit/3fbc7cd331602c76f882d1b507cd05c1d824ba8b [1a] https://gitorious.org/fetchmail/fetchmail/commit/c189f6a54f36f5b6f7734303db3cfc52311aab5f [1b] https://gitorious.org/fetchmail/fetchmail/commit/b3e0cd2d558b5ccf06c816eed38c883d7462d3d4 Upstream advisory (not available yet):  http://www.fetchmail.info/fetchmail-SA-2012-02.txt CVE request:  http://www.openwall.com/lists/oss-security/2012/08/13/9 References:  https://bugs.gentoo.org/show_bug.cgi?id=431284
Comment 1 Jan Lieskovsky 2012-08-14 05:34:54 EDT
This issue affects the versions of the fetchmail package, as shipped with Fedora release of 16 and 17. Please schedule an update.
Comment 2 Jan Lieskovsky 2012-08-14 05:35:45 EDT
Created fetchmail tracking bugs for this issue Affects: fedora-all [bug 847989]
Comment 4 Fedora Update System 2012-10-02 11:57:13 EDT
fetchmail-6.3.22-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
Comment 5 Stefan Cornelius 2012-10-05 03:11:25 EDT
Statement: The Red Hat Security Response Team has rated this issue as having low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.