Debian has issued an advisory today (January 6): https://www.debian.org/security/2015/dsa-3119 The issue is fixed upstream in 2.0.22: http://archives.seul.org/libevent/users/Jan-2015/msg00012.html Freeze push requested for Cauldron. Patched package uploaded for Mageia 4. Advisory: ======================== Updated libevent packages fix security vulnerability: Andrew Bartlett of Catalyst reported a defect affecting certain applications using the Libevent evbuffer API. This defect leaves applications which pass insanely large inputs to evbuffers open to a possible heap overflow or infinite loop. In order to exploit this flaw, an attacker needs to be able to find a way to provoke the program into trying to make a buffer chunk larger than what will fit into a single size_t or off_t (CVE-2014-6272). References: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6272 https://www.debian.org/security/2015/dsa-3119 ======================== Updated packages in core/updates_testing: ======================== libevent5-2.0.21-5.1.mga4 libevent-devel-2.0.21-5.1.mga4 from libevent-2.0.21-5.1.mga4.src.rpm Reproducible: Steps to Reproduce:
Severity: normal => major
MGA4-64 on HP Probook 6555b KDE No installation issues. libevent is required a.o. by firefox. Is submitting this comment enough to OK it?
CC: (none) => herman.viaene
OK 64 bit unless other PoC comes up.
Whiteboard: (none) => MGA4-64-OK
MGA4-32 on AcerD620 Xfce. No installation issues. Same test as Comment 1.
Whiteboard: MGA4-64-OK => MGA4-64-OK MGA4-32-OK
If its not generating any errors Herman, yes. There are also thunderbird, iceape, tor and transmission which use it. You could possibly show the library being loaded using strace.
No errors have occured. Using strace now to check this update.
libevent5.so is called twice, thus should be OK.
Well done Herman. Validating. Advisory uploaded. Please push to 4 updates Thanks
Keywords: (none) => validated_updateWhiteboard: MGA4-64-OK MGA4-32-OK => has_procedure advisory MGA4-64-OK MGA4-32-OKCC: (none) => sysadmin-bugs
An update for this issue has been pushed to Mageia Updates repository. http://advisories.mageia.org/MGASA-2015-0009.html
Status: NEW => RESOLVEDResolution: (none) => FIXED