dbcve.org
Qpid CppApplication · Apache

CVE-2014-0212

HIGH · 7.5 CVSS v3.1 Published 2019-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

In qpid-cpp (Apache Qpid C++ message broker), ACL (Access Control List) policies are only loaded when the acl-file option is explicitly specified in the configuration. When this option is not set, no ACL enforcement occurs, leaving the broker unprotected. This default behavior enables an attacker to cause a Denial of Service by consuming all available file descriptors without any access controls being applied.

MitigationConfigure the acl-file option to explicitly load ACL policies, or modify the code to enforce ACL by default rather than requiring explicit configuration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Qpid CppApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify qpid-cpp installation
    Locate the qpid-cpp broker binary and confirm it is installed (e.g., which qpidd, rpm -q qpid-cpp, or ps aux | grep qpidd)
    Affected if qpid-cpp is installed and running but no acl-file option is configured
  2. Locate broker configuration
    Find the configuration file used by the broker (commonly /etc/qpid/qpidd.conf or similar), or check the process command line arguments
    Affected if Configuration file exists but does not contain an acl-file directive
  3. Check for acl-file option
    Inspect the configuration file and any command-line arguments for the acl-file option (e.g., grep -i acl-file <configfile> or ps aux | grep qpidd)
    Affected if The acl-file option is not present or not set to a valid ACL policy file path
  4. Verify ACL enforcement is active
    If acl-file is set, confirm the specified ACL file exists and the broker is enforcing ACL rules (e.g., check broker logs for ACL loading, or test with an unauthorized request)
    Affected if ACL file is not explicitly configured, meaning no access control is being applied

You are affected if the qpid-cpp broker is running without the acl-file option explicitly configured in its configuration file or command line, leaving ACL enforcement completely disabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Configure the acl-file option to explicitly load ACL policies, or modify the code to enforce ACL by default rather than requiring explicit configuration.

Fix this in Qpid Cpp Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-0212 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-0212 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data