CVE-2015-0224

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

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

• collector/nvd-index
• agent/references
• agent/severity
• agent/weakness
• agent/author
• agent/event
• agent/type
• agent/description
• agent/remedy
• agent/last-modified-date
• agent/softwarecombine
• agent/first-publish-date
• agent/tags
• collector/redhat-bugzilla
• source/Red Hat
• alias/CVE-2015-0224
• collector/mitre-cve
• source/MITRE
• vendor/apache
• canonical/apache qpid
• version/apache qpid/0.30