A security flaw was found in the XMPP Dialback protocol implementation of jabberd2, OpenSource server implementation of the Jabber protocols (Verify Response and Authorization Response were not checked within XMPP protocol server to server session). A rogue XMPP server could use this flaw to spoof one or more domains, when communicating with vulnerable server implementation, possibly leading into XMPP's Server Dialback protections bypass. References: [1] http://xmpp.org/resources/security-notices/server-dialback/ Upstream patch: [2] https://github.com/Jabberd2/jabberd2/commit/aabcffae560d5fd00cd1d2ffce5d760353cf0a4d
This issue has been corrected in the (upcoming) Fedora and Fedora EPEL jabberd packages: Rawhide: jabberd-2.2.16-5.fc18 Fedora-17: jabberd-2.2.14-4.fc17 Fedora-16: jabberd-2.2.14-4.fc16 Fedora EPEL 6: jabberd-2.2.14-4.el6 Fedora EPEL 5: jabberd-2.2.11-4.el5
This issue affects the versions of the jabberd package, as shipped with Red Hat Network Satellite Server 5.4 and with Red Hat Network Proxy Server 5.4.
CVE request: http://www.openwall.com/lists/oss-security/2012/08/22/5
The CVE identifier of CVE-2012-3525 has been assigned to this issue: http://www.openwall.com/lists/oss-security/2012/08/22/6
jabberd-2.2.14-4.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
jabberd-2.2.14-4.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
jabberd-2.2.11-4.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.
jabberd-2.2.14-4.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
jabberd-2.2.17-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
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/.
This issue has been addressed in following products: Red Hat Network Proxy v 5.5 Via RHSA-2012:1539 https://rhn.redhat.com/errata/RHSA-2012-1539.html
This issue has been addressed in following products: Red Hat Network Satellite Server v 5.5 Via RHSA-2012:1538 https://rhn.redhat.com/errata/RHSA-2012-1538.html