CVE-2015-0224: High severity apache qpid vulnerability

Published Jan 27, 2015
·
Updated

In CVE-2015-0203 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 (https://issues.apache.org/jira/browse/QPID-6310). The fix will be included in subsequent releases, but can be applied to 0.30 if desired.

Other sources

qpidd in Apache Qpid 0.30 and earlier allows remote attackers to cause a denial of service (daemon crash) via a crafted protocol sequence set. NOTE: this vulnerability exists because of an incomplete fix for CVE-2015-0203.

MITRE

Affected Software

1 affected component
Apache qpid<=0.30

Event History

Jan 27, 2015
Data Sourced
via Red Hat·11:34 AM
DescriptionSeverityAffected Software
Oct 30, 2017
CVE Published
via MITRE·02:00 PM
Data Sourced
via MITRE·02:00 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2015-0224?

CVE-2015-0224 has been classified as a fair severity vulnerability due to its potential to cause crashes in the broker process.

2

How do I fix CVE-2015-0224?

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.

3

What are the impacts of exploiting CVE-2015-0224?

Exploiting CVE-2015-0224 can lead to crashes of the broker process, potentially disrupting service.

4

Is CVE-2015-0224 affected by authentication measures?

Yes, while authentication may restrict exploitation, it doesn't eliminate the vulnerability posed by CVE-2015-0224.

5

Which versions of Apache Qpid are affected by CVE-2015-0224?

CVE-2015-0224 affects Apache Qpid versions up to and including 0.30.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203