First published: Wed Aug 22 2012(Updated: )
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] <a href="http://xmpp.org/resources/security-notices/server-dialback/">http://xmpp.org/resources/security-notices/server-dialback/</a> Upstream patch: [2] <a href="https://github.com/Jabberd2/jabberd2/commit/aabcffae560d5fd00cd1d2ffce5d760353cf0a4d">https://github.com/Jabberd2/jabberd2/commit/aabcffae560d5fd00cd1d2ffce5d760353cf0a4d</a>
Affected Software | Affected Version | How to fix |
---|---|---|
jabberd2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-850872 is considered critical due to the potential for spoofing and unauthorized access.
To fix REDHAT-BUG-850872, update to the latest version of jabberd2 where the vulnerability has been patched.
Users of jabberd2 may be at risk of allowing rogue servers to spoof valid communications if REDHAT-BUG-850872 is not addressed.
Yes, using a previous version of jabberd2 leaves systems vulnerable to the exploits related to REDHAT-BUG-850872.
REDHAT-BUG-850872 was identified and reported within the context of security assessments for jabberd2.