Skip to content
Fencer Intel
medium 5.0

CVE-2012-4460 json

The serializing/deserializing functions in the qpid::framing::Buffer class in Apache Qpid 0.20 and earlier allow remote attackers to cause…

published 2013-03-12 13 y ago modified 2026-06-16 4 mo ago also EUVD-2012-4389

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.2%
EPSS 3.2% chance of exploitation in 30 days, percentile 88%
public exploits
0
none known

Summary

The serializing/deserializing functions in the qpid::framing::Buffer class in Apache Qpid 0.20 and earlier allow remote attackers to cause a denial of service (assertion failure and daemon exit) via unspecified vectors. NOTE: this issue could also trigger an out-of-bounds read, but it might not trigger a crash.

Patch / fix

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2012-4460 updated cvss 5.0

qpid-cpp: lack of bounds checking in qpid::framing::Buffer can lead to DoS if asserts are enabled

  • Red Hat Enterprise Linux 6 qpid-cpp, qpid-cpp-client, qpid-cpp-server, qpid-cpp-client-ssl, qpid-cpp-server-ssl, qpid-cpp-server-xml, +4 more Red Hat Enterprise MRG 1 qpid-cpp Red Hat Enterprise MRG 2 qpid-cpp, qpid-cpp-client, qpid-cpp-server, qpid-cpp-client-ssl, qpid-cpp-server-ssl, qpid-cpp-server-xml, +4 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

3.18% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.