CVE-2012-3525: Input Validation
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
Other sources
s2s/out.c in jabberd2 2.2.16 and earlier does not verify that a request was made for an XMPP Server Dialback response, which allows remote XMPP servers to spoof domains via a (1) Verify Response or (2) Authorization Response.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2012-3525?
CVE-2012-3525 has been rated as a high severity vulnerability due to its potential for spoofing and denial of service attacks.
How do I fix CVE-2012-3525?
To fix CVE-2012-3525, upgrade jabberd2 to version 2.2.16 or later to ensure proper verification of responses in the XMPP Dialback protocol.
What software is affected by CVE-2012-3525?
CVE-2012-3525 affects jabberd2 versions from 2.1.0 to 2.2.15, including all specific releases in this range.
Can CVE-2012-3525 lead to data leakage?
Yes, CVE-2012-3525 can allow a rogue XMPP server to potentially spoof connections and impersonate valid servers, leading to data leakage.
Is there a workaround for CVE-2012-3525 if I cannot upgrade jabberd2?
While upgrading is the best option, consider implementing strict firewall rules to limit access to the jabberd2 service as a temporary workaround.