dbcve.org
QpidApplication · Apache

CVE-2012-2145

MEDIUM · 5.0 CVSS v2.0 Published 2012-09-28
Fix available
A fix is available. Upgrade to after 0.17 or later.
See remediation →
59/100
Remediation priority · Elevated
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
Apache Qpid 0.17 and earlier does not properly restrict incoming client connections, which allows remote attackers to cause a denial of service (file descriptor consumption) via a large number of incomplete connections.

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

Apache Qpid versions 0.17 and earlier fail to impose proper restrictions on incoming client connections, enabling remote attackers to trigger a denial of service condition through exhaustion of file descriptors via a large volume of incomplete connection attempts.

MitigationImplement connection rate limiting, configure appropriate connection thresholds, and consider deploying firewall rules or a load balancer to filter malicious connection patterns before they reach the Qpid service.

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
QpidApplication
Affected:<= 0.17= 0.6= 0.7= 0.8= 0.9= 0.10= 0.12= 0.14= 0.16

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
Authentication
None
Confidentiality
None
Integrity
None
Availability
Partial

AV:N/AC:L/Au:N/C:N/I:N/A:P

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 if Apache Qpid is installed
    Run 'qpid-config' or 'qpidd --version' to check for Qpid installation, or search for qpidd binary using 'which qpidd' or 'find /usr -name "qpidd" 2>/dev/null'
    Affected if No qpidd binary found means Qpid is not installed and this CVE does not apply
  2. Determine the installed Qpid version
    Execute 'qpidd --version' or 'qpidd --help' to retrieve the version number, or check package manager output like 'rpm -q qpid-cpp' or 'dpkg -l | grep qpid'
    Affected if Version is 0.17 or earlier (including 0.6, 0.7, 0.8, 0.9, 0.10, 0.12, 0.14, 0.16) - compare your installed version to the affected ranges listed in the CVE
  3. Verify if Qpid service is network accessible
    Check listening ports using 'netstat -tlnp | grep qpid' or 'ss -tlnp | grep qpid', and review firewall rules or bind addresses in Qpid configuration files
    Affected if The service is exposed to untrusted networks (0.0.0.0 or external interfaces) - remote attackers must be able to send connection attempts to exploit this flaw
  4. Check current file descriptor limits
    Run 'ulimit -n' for current session limits, and check '/etc/security/limits.conf' or systemd service files for configured limits applicable to the qpidd process
    Affected if File descriptor limits are set very high or unlimited (e.g., 65536+) without connection rate limiting configured - higher limits enable larger DoS impact
  5. Inspect Qpid connection configuration settings
    Review Qpid configuration files (typically in /etc/qpid/ or /var/lib/qpid/) for connection-related settings such as max-connections, connection-timeout, or rate-limiting options
    Affected if No connection rate limiting or max-connection restrictions are configured - the vulnerability exists precisely when these restrictions are absent or insufficient

You are affected if Apache Qpid version 0.17 or earlier is installed, exposed to network, and has no connection rate limiting or file descriptor restrictions configured.

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
Upgrade available Upgrade to a release after 0.17
Interim mitigation

Implement connection rate limiting, configure appropriate connection thresholds, and consider deploying firewall rules or a load balancer to filter malicious connection patterns before they reach the Qpid service.

Fix this in Qpid Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-2145 — 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-2012-2145 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