First published: Tue Jan 27 2015(Updated: )
In <a href="https://access.redhat.com/security/cve/CVE-2015-0203">CVE-2015-0203</a> it was announced that certain unexpected protocol sequences cause the broker process to crash due to insufficient checking, but that authentication could be used to restrict the exploitation of this vulnerability. It has now been discovered that in fact failing authentication does not necessarily prevent exploitation of those reported vulnerabilities. Further, it was stated that one of the specific vulnerabilities was that the qpidd broker can be crashed by sending it a sequence-set containing an invalid range, where the start of the range is after the end. This was an incorrect analysis of the vulnerability, which is in fact caused by a sequence-set containing a single range expressing the maximum possible gap. A further patch is available that handles a range expressing the maximum possible gap without assertion (<a href="https://issues.apache.org/jira/browse/QPID-6310">https://issues.apache.org/jira/browse/QPID-6310</a>). The fix will be included in subsequent releases, but can be applied to 0.30 if desired.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Apache Qpid | <=0.30 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2015-0224 has been classified as a fair severity vulnerability due to its potential to cause crashes in the broker process.
To address CVE-2015-0224, it's recommended to update Apache Qpid to a version later than 0.30 where the vulnerability has been patched.
Exploiting CVE-2015-0224 can lead to crashes of the broker process, potentially disrupting service.
Yes, while authentication may restrict exploitation, it doesn't eliminate the vulnerability posed by CVE-2015-0224.
CVE-2015-0224 affects Apache Qpid versions up to and including 0.30.