Skip to content
Fencer Intel
high 7.5

CVE-2014-0212 json

qpid-cpp: ACL policies only loaded if the acl-file option specified enabling DoS by consuming all available file descriptors

published 6y ago modified 4mo ago also EUVD-2014-0262

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
4.0%
EPSS 4.0% chance of exploitation in 30 days, percentile 90%
public exploits
0
none known

Summary

qpid-cpp: ACL policies only loaded if the acl-file option specified enabling DoS by consuming all available file descriptors

Is CVE-2014-0212 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2014-0212 updated cvss 5.0

qpid-cpp: on-demand ACL policy loading enables a denial of service by consuming all available file descriptors

  • 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 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.99% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Affected products

  • qpid-cpp qpid-cpp

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption

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.