CVE-2012-4458
qpid-cpp: long arrays of zero-width types cause a denial of service
Overview
Description
The AMQP type decoder in Apache Qpid 0.20 and earlier allows remote attackers to cause a denial of service (memory consumption and server crash) via a large number of zero width elements in the client-properties map in a connection.start-ok message.
Source: OX vulnerability database
Severity
5 · MEDIUM
CVSS 2.0 base score, scored by NVD.
- Access vector
- Network
- Access complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
Weakness: CWE-189
Affected packages · 0
No registry package. This ID affects operating system packages only.
Operating systems · 13 fixes
Red Hat 1 release · 13 packages
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| cumin-messaging | 0:0.1.1-2.el6 | RHSA-2013:0562 | |
| python-saslwrapper +3 | 0:0.18-1.el6_3 | RHSA-2013:0562 | |
| qpid-cpp-client +11 | 0:0.18-14.el6 | RHSA-2013:0562 | |
| python-qpid-qmf +3 | 0:0.18-15.el6 | RHSA-2013:0562 | |
| qpid-tests +1 | 0:0.18-2.el6 | RHSA-2013:0562 | |
| python-qpid | 0:0.18-4.el6 | RHSA-2013:0562 |
7 more rows
References
- rhn.redhat.com http://rhn.redhat.com/errata/RHSA-2013-0561.html
- rhn.redhat.com http://rhn.redhat.com/errata/RHSA-2013-0562.html
- secunia.com http://secunia.com/advisories/52516
- svn.apache.org http://svn.apache.org/viewvc?view=revision&revision=1453031
- access.redhat.com https://access.redhat.com/security/cve/CVE-2012-4458
- bugzilla.redhat.com https://bugzilla.redhat.com/show_bug.cgi?id=861234
- issues.apache.org https://issues.apache.org/jira/browse/QPID-4629
- issues.apache.org https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%20%220.21%22%20AND%20project%20%3D%20QPID
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2012-4458
- www.cve.org https://www.cve.org/CVERecord?id=CVE-2012-4458
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.