Vulnerability Note VU#489228

Ignite Realtime Smack XMPP API contains multiple vulnerabilities

Original Release date: 29 Apr 2014 | Last revised: 29 Apr 2014

Overview

Ignite Realtime's Smack XMPP API ServerTrustManger trusts unauthorized SSL certificates (CWE-358) and IQ requests do not verify the from attribute allowing anyone to spoof IQ responses. (CWE-345)

Description

CWE-358: Improperly Implemented Security Check for Standard - CVE-2014-0363

The implementation of ServerTrustManger in Smack API version 3.4.1, and possibly earlier versions, does not properly verify the basicConstraints and nameConstraints of a certificate within a certificate chain.

CWE-345: Insufficient Verification of Data Authenticity - CVE-2014-0364
The implementation of ParseRoster in Smack API version 3.4.1, and possibly earlier versions, does not properly verify the from attribute for roster queries.

The CVSS score below is for CVE-2014-0363.

Impact

A remote unauthenticated attacker may be able to perform a man-in-the-middle attack, add roster entries or spoof IQ responses.

Solution

Apply an Update

Smack API version 4.0.0 addresses these vulnerabilities. At the time of publication only a release candidate for version 4.0.0 was available.

Vendor Information (Learn More)

VendorStatusDate NotifiedDate Updated
Ignite RealtimeAffected-29 Apr 2014
If you are a vendor and your product is affected, let us know.

CVSS Metrics (Learn More)

Group Score Vector
Base 5.7 AV:A/AC:M/Au:N/C:C/I:N/A:N
Temporal 4.5 E:POC/RL:OF/RC:C
Environmental 5.5 CDP:LM/TD:M/CR:H/IR:L/AR:L

References

Credit

Thanks to Ryan Sleevi for identifying the vulnerability in ServerTrustManager and Thijs Alkemade for identifying the IQ validation vulnerability and Florian Schmaus for reporting this vulnerability.

This document was written by Jared Allar.

Other Information

  • CVE IDs: CVE-2014-0363 CVE-2014-0364
  • Date Public: 29 Apr 2014
  • Date First Published: 29 Apr 2014
  • Date Last Updated: 29 Apr 2014
  • Document Revision: 15

Feedback

If you have feedback, comments, or additional information about this vulnerability, please send us email.