Qpid CppApplication · Apache
CVE-2009-5004
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 · uneditedqpid-cpp 1.0 crashes when a large message is sent and the Digest-MD5 mechanism with a security layer is in use .
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 confidenceIn qpid-cpp 1.0, sending a large message while using the Digest-MD5 authentication mechanism with a security layer enabled triggers a crash, resulting in denial of service. The vulnerability stems from improper handling of message size boundaries within the Digest-MD5 security layer implementation.
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
= 1.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed qpid-cpp versionRun 'rpm -q qpid-cpp' or check the installed package version through your package manager. For source installations, check the version string in the binary or compile-time headers.Affected if The installed version is exactly 1.0
-
Verify Digest-MD5 authentication is configuredExamine the qpid broker or client configuration files (typically in /etc/qpid or the application's config) for 'DIGEST-MD5' or 'digest-md5' in the authentication settings.Affected if Digest-MD5 is listed as an enabled or available authentication mechanism
-
Confirm security layer is enabledCheck the qpid configuration for security layer settings. This may appear as 'security layer', 'encryption', or 'ssf' (simple security factor) parameters in the broker or connection settings.Affected if A security layer is configured alongside Digest-MD5 authentication
-
Review message size configurationsInspect qpid broker and client settings for maximum message size limits or message size-related parameters in the configuration files.Affected if Large or unlimited message sizes are permitted in the configuration
A system is affected if it runs qpid-cpp version 1.0 with Digest-MD5 authentication and a security layer enabled, allowing large message sizes.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade qpid-cpp to a version where this vulnerability is patched. If upgrading is not immediately feasible, avoid using the Digest-MD5 mechanism with security layers or limit incoming message sizes as a temporary workaround.
Fix this in Qpid Cpp
Scoped from the published advisory
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-5004 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2009-5004 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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