QpidApplication · Apache
CVE-2012-3467
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 · uneditedApache QPID 0.14, 0.16, and earlier uses a NullAuthenticator mechanism to authenticate catch-up shadow connections to AMQP brokers, which allows remote attackers to bypass authentication.
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 confidenceApache QPID versions 0.14, 0.16, and earlier contain a NullAuthenticator mechanism used for authenticating catch-up shadow connections to AMQP brokers. This mechanism essentially bypasses authentication entirely, allowing any remote attacker to connect to the broker without providing credentials.
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
<= 0.16= 0.5= 0.6= 0.14CVSS 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
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/A:N
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 Apache QPID installation and versionRun 'qpidd --version' or check package manager for installed qpid packages. Compare the version to affected ranges: 0.14, 0.16, 0.5, 0.6, and any version <= 0.16Affected if The installed version is 0.14, 0.16, 0.5, 0.6, or any version <= 0.16
-
Locate QPID configuration filesSearch for qpid configuration files in standard locations such as /etc/qpid/, /etc/opt/, or the working directory where qpidd is run. Look for .conf, .xml, or config files used by the broker.Affected if Configuration files exist and contain authentication-related settings
-
Check for NullAuthenticator mechanismInspect the broker configuration for any entries referencing 'NullAuthenticator', 'null', or authentication mechanisms that bypass credential verification. Look for settings that allow unauthenticated connections, particularly for shadow or catch-up connections.Affected if NullAuthenticator is enabled or any mechanism allowing unauthenticated connections is configured
-
Verify authentication enforcement on AMQP portsReview the broker's listening ports and connection settings to confirm whether all connections, including internal shadow/catch-up connections, are required to provide valid credentials.Affected if Shadow or catch-up connections can be established without providing credentials
If the installed QPID version falls within 0.5, 0.6, 0.14, 0.16, or any version <= 0.16 AND the NullAuthenticator or an unauthenticated connection mechanism is configured, the broker is vulnerable to unauthenticated remote access.
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 dataDisable or remove the NullAuthenticator mechanism and ensure all connections, including shadow/catch-up connections, require proper authentication. Consider upgrading to a patched version of QPID if available.
Fix this in Qpid
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-3467 — 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-2012-3467 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