CVE-2015-0224

Description

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.

Category

7.5
CVSS
Severity: High
CVSS 3.0 •
CVSS 2.0 •
EPSS 56.01% Top 5%
Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory fedoraproject.org Vendor Advisory redhat.com Vendor Advisory apache.org
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://access.redhat.com/errata/RHBA-2016:1500 vendor advisory
https://issues.apache.org/jira/browse/QPID-6310 patch vendor advisory issue tracking
http://www.securitytracker.com/id/1031872 third party advisory vdb entry issue tracking
https://access.redhat.com/errata/RHSA-2015:0708 vendor advisory third party advisory issue tracking
http://www.securityfocus.com/bid/72317 third party advisory vdb entry issue tracking
http://rhn.redhat.com/errata/RHSA-2015-0661.html vendor advisory third party advisory issue tracking
http://www.securityfocus.com/archive/1/534545/100/0/threaded mailing list
http://rhn.redhat.com/errata/RHSA-2015-0662.html vendor advisory third party advisory issue tracking
http://packetstormsecurity.com/files/130105/Apache-Qpid-0.30-Crash.html third party advisory vdb entry issue tracking
http://mail-archives.apache.org/mod_mbox/www-announce/201501.mbox/%3C54C60497.5060504%40apache.org%3E mailing list
http://rhn.redhat.com/errata/RHSA-2015-0660.html vendor advisory third party advisory issue tracking
https://bugzilla.redhat.com/show_bug.cgi?id=1186302 third party advisory issue tracking
http://lists.fedoraproject.org/pipermail/package-announce/2016-March/178606.html vendor advisory third party advisory issue tracking
http://rhn.redhat.com/errata/RHSA-2015-0707.html vendor advisory third party advisory issue tracking

Frequently Asked Questions

What is the severity of CVE-2015-0224?
CVE-2015-0224 has been scored as a high severity vulnerability.
How to fix CVE-2015-0224?
To fix CVE-2015-0224, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2015-0224 being actively exploited in the wild?
It is possible that CVE-2015-0224 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~56% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.