medium
5.8
CWE
20
Advisory Published
CVE Published
Updated

CVE-2012-3525: Input Validation

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>

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
Jabberd=2.1.19
Jabberd<=2.2.16
Jabberd=2.1
Jabberd=2.1.1
Jabberd=2.1.2
Jabberd=2.1.3
Jabberd=2.1.4
Jabberd=2.1.5
Jabberd=2.1.6
Jabberd=2.1.7
Jabberd=2.1.8
Jabberd=2.1.9
Jabberd=2.1.10
Jabberd=2.1.11
Jabberd=2.1.12
Jabberd=2.1.13
Jabberd=2.1.14
Jabberd=2.1.15
Jabberd=2.1.16
Jabberd=2.1.17
Jabberd=2.1.18
Jabberd=2.1.20
Jabberd=2.1.21
Jabberd=2.1.22
Jabberd=2.1.23
Jabberd=2.1.24
Jabberd=2.2.0
Jabberd=2.2.1
Jabberd=2.2.2
Jabberd=2.2.3
Jabberd=2.2.4
Jabberd=2.2.5
Jabberd=2.2.6
Jabberd=2.2.7
Jabberd=2.2.7.1
Jabberd=2.2.8
Jabberd=2.2.9
Jabberd=2.2.10
Jabberd=2.2.11
Jabberd=2.2.12
Jabberd=2.2.13
Jabberd=2.2.14
Jabberd=2.2.15

Remedy

https://github.com/Jabberd2/jabberd2/commit/aabcffae560d5fd00cd1d2ffce5d760353cf0a4d

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

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.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203