Multiple heap-based buffer overflow flaws were found in the way the Base64 decoder of libotr, an Off-The-Record Messaging library and toolkit, performed decoding of certain messages. A remote attacker could provide a specially-crafted OTR message that once processed in an application linked against libotr would lead to that application crash or, potentially, arbitrary code execution with the privileges of the user running the application. References: [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684121 [2] http://lists.cypherpunks.ca/pipermail/otr-dev/2012-July/001347.html Relevant upstream patches: [3] http://otr.git.sourceforge.net/git/gitweb.cgi?p=otr/libotr;a=commitdiff;h=b17232f86f8e60d0d22caf9a2400494d3c77da58 [4] http://otr.git.sourceforge.net/git/gitweb.cgi?p=otr/libotr;a=commitdiff;h=6d4ca89cf1d3c9a8aff696c3a846ac5a51f762c1 [5] http://otr.git.sourceforge.net/git/gitweb.cgi?p=otr/libotr;a=commitdiff;h=1902baee5d4b056850274ed0fa8c2409f1187435
These issues affect the versions of the libotr package, as shipped with Fedora release of 16 and 17. Please schedule an update. -- These issues affect the versions of the libotr package, as shipped with Fedora EPEL 5 and 6. Please schedule an update.
Created libotr tracking bugs for this issue Affects: fedora-all [bug 846380] Affects: epel-all [bug 846381]
I'm talking with upstream. They only released a patch, which also increases the version number of the release, without releasing a tar ball. I'm trying to convince them to do a proper tar ball release.
bodhi didn't update bugzilla, but Fedora builds have been made. EL builds will follow soon. https://admin.fedoraproject.org/updates/libotr-3.2.0-7.fc16 https://admin.fedoraproject.org/updates/libotr-3.2.0-8.fc17
The CVE identifier of CVE-2012-3461 has been assigned to these issues: http://www.openwall.com/lists/oss-security/2012/08/08/3
(In reply to comment #4) > bodhi didn't update bugzilla, but Fedora builds have been made. EL builds > will follow soon. > > > https://admin.fedoraproject.org/updates/libotr-3.2.0-7.fc16 > https://admin.fedoraproject.org/updates/libotr-3.2.0-8.fc17 Thanks, Paul (I suspect both of the bug ids, thus #846377 and #846380 need to be listed when scheduling Bodhi update request).
https://admin.fedoraproject.org/updates/libotr-3.2.0-5.el6 https://admin.fedoraproject.org/updates/libotr-3.2.0-2.el5 (apparently security marked bugs get their announcements delayed on purpose)
there is updated version of this patch, which is included in a new version of libotr (and pidgin-otr), despite earlier plans of upstream to not release a new version, I'm building this now and tomorrow
builds are in testing. note there is no new CVE planned for the difference between the two patches.
libotr-3.2.1-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
libotr-3.2.1-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
libotr-3.2.1-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.
libotr-3.2.1-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
libotr-3.2.1-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.