The default configuration for Apache Qpid 0.20 and earlier, when the federation_tag attribute is enabled, accepts AMQP connections without c
The default configuration for Apache Qpid 0.20 and earlier, when the federation_tag attribute is enabled, accepts AMQP connections without checking the source user ID, which allows remote attackers to bypass authentication and have other unspecified impact via an AMQP request.
- Published
- Mar 13, 2013
- Updated
- Jun 16, 2026
- EPSS
- 4.9% · 92th percentile
- CWE
- CWE-287
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.9%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| apache | qpid | cpe:2.3:a:apache:qpid |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- apache qpidup to 0.20 inclusive
- apache qpid0.10
- apache qpid0.11
- apache qpid0.12
- apache qpid0.13
- apache qpid0.14
- apache qpid0.15
- apache qpid0.16
- apache qpid0.17
- apache qpid0.18
- apache qpid0.19
- apache qpid0.5
- apache qpid0.6
- apache qpid0.7
- apache qpid0.8
- apache qpid0.9
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | org.apache.qpid:qpid-client | before 0.20 | 0.20 |
| Red Hat:enterprise_mrg:2::el5 | cumin-messaging | before 0:0.1.1-2.el5 | 0:0.1.1-2.el5 |
| Red Hat:enterprise_mrg:2::el5 | mrg-release | before 0:2.3.0-1.el5 | 0:2.3.0-1.el5 |
| Red Hat:enterprise_mrg:2::el5 | python-qpid | before 0:0.18-4.el5 | 0:0.18-4.el5 |
| Red Hat:enterprise_mrg:2::el5 | python-qpid-qmf | before 0:0.18-15.el5 | 0:0.18-15.el5 |
| Red Hat:enterprise_mrg:2::el5 | python-saslwrapper | before 0:0.18-1.el5 | 0:0.18-1.el5 |
| Red Hat:enterprise_mrg:2::el5 | qpid-cpp-client | before 0:0.18-14.el5 | 0:0.18-14.el5 |
| Red Hat:enterprise_mrg:2::el5 | qpid-cpp-client-devel | before 0:0.18-14.el5 | 0:0.18-14.el5 |
| Red Hat:enterprise_mrg:2::el5 | qpid-cpp-client-devel-docs | before 0:0.18-14.el5 | 0:0.18-14.el5 |
| Red Hat:enterprise_mrg:2::el5 | qpid-cpp-client-rdma | before 0:0.18-14.el5 | 0:0.18-14.el5 |
| Red Hat:enterprise_mrg:2::el5 | qpid-cpp-client-ssl | before 0:0.18-14.el5 | 0:0.18-14.el5 |
| Red Hat:enterprise_mrg:2::el5 | qpid-cpp-mrg | before 0:0.18-14.el5 | 0:0.18-14.el5 |
| Red Hat:enterprise_mrg:2::el5 | qpid-cpp-mrg-debuginfo | before 0:0.18-14.el5 | 0:0.18-14.el5 |
| Red Hat:enterprise_mrg:2::el5 | qpid-cpp-server | before 0:0.18-14.el5 | 0:0.18-14.el5 |
| Red Hat:enterprise_mrg:2::el5 | qpid-cpp-server-cluster | before 0:0.18-14.el5 | 0:0.18-14.el5 |
| Red Hat:enterprise_mrg:2::el5 | qpid-cpp-server-devel | before 0:0.18-14.el5 | 0:0.18-14.el5 |
| Red Hat:enterprise_mrg:2::el5 | qpid-cpp-server-rdma | before 0:0.18-14.el5 | 0:0.18-14.el5 |
| Red Hat:enterprise_mrg:2::el5 | qpid-cpp-server-ssl | before 0:0.18-14.el5 | 0:0.18-14.el5 |
| Red Hat:enterprise_mrg:2::el5 | qpid-cpp-server-store | before 0:0.18-14.el5 | 0:0.18-14.el5 |
| Red Hat:enterprise_mrg:2::el5 | qpid-cpp-server-xml | before 0:0.18-14.el5 | 0:0.18-14.el5 |
| Red Hat:enterprise_mrg:2::el5 | qpid-java | before 0:0.18-7.el5 | 0:0.18-7.el5 |
| Red Hat:enterprise_mrg:2::el5 | qpid-java-client | before 0:0.18-7.el5 | 0:0.18-7.el5 |
| Red Hat:enterprise_mrg:2::el5 | qpid-java-common | before 0:0.18-7.el5 | 0:0.18-7.el5 |
| Red Hat:enterprise_mrg:2::el5 | qpid-java-example | before 0:0.18-7.el5 | 0:0.18-7.el5 |
+59
Same product
apache: all recordsOther highest-scoring records for the same primary product.
- CVE-2015-0224qpidd in Apache Qpid 0.30 and earlier allows remote attackers to cause a denial of service (daemon crash) via a crafted protocol sequence se35Monitor
- CVE-2011-3620Apache Qpid 0.12 does not properly verify credentials during the joining of a cluster, which allows remote attackers to obtain access to the32Monitor
- CVE-2019-0223While investigating bug PROTON-2014, we discovered that under some circumstances Apache Qpid Proton versions 0.9 to 0.27.0 (C library and it31Monitor
- CVE-2015-0203The qpidd broker in Apache Qpid 0.30 and earlier allows remote authenticated users to cause a denial of service (daemon crash) via an AMQP m29Monitor
- CVE-2013-1909The Python client in Apache Qpid before 2.2 does not verify that the server hostname matches a domain name in the subject's Common Name (CN)23Monitor
- CVE-2012-4459Integer overflow in the qpid::framing::Buffer::checkAvailable function in Apache Qpid 0.20 and earlier allows remote attackers to cause a de23Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:org.apache.qpid:qpid-client | 0.20 | Package registry (OSV) |
| red hat:cumin-messaging | 0:0.1.1-2.el5 · Red Hat:enterprise_mrg:2::el5 | Package registry (OSV) |
| red hat:mrg-release | 0:2.3.0-1.el5 · Red Hat:enterprise_mrg:2::el5 | Package registry (OSV) |
| red hat:python-qpid | 0:0.18-4.el5 · Red Hat:enterprise_mrg:2::el5 | Package registry (OSV) |
| red hat:python-qpid-qmf | 0:0.18-15.el5 · Red Hat:enterprise_mrg:2::el5 | Package registry (OSV) |
| red hat:python-saslwrapper | 0:0.18-1.el5 · Red Hat:enterprise_mrg:2::el5 | Package registry (OSV) |
| red hat:qpid-cpp-client | 0:0.18-14.el5 · Red Hat:enterprise_mrg:2::el5 | Package registry (OSV) |
| red hat:qpid-cpp-client-devel | 0:0.18-14.el5 · Red Hat:enterprise_mrg:2::el5 | Package registry (OSV) |
| red hat:qpid-cpp-client-devel-docs | 0:0.18-14.el5 · Red Hat:enterprise_mrg:2::el5 | Package registry (OSV) |
| red hat:qpid-cpp-client-rdma | 0:0.18-14.el5 · Red Hat:enterprise_mrg:2::el5 | Package registry (OSV) |
| red hat:qpid-cpp-client-ssl | 0:0.18-14.el5 · Red Hat:enterprise_mrg:2::el5 | Package registry (OSV) |
| red hat:qpid-cpp-mrg | 0:0.18-14.el5 · Red Hat:enterprise_mrg:2::el5 | Package registry (OSV) |
| red hat:qpid-cpp-mrg-debuginfo | 0:0.18-14.el5 · Red Hat:enterprise_mrg:2::el5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- P · the service can be disrupted
- Attack complexity
- M
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- P
Weakness class (CWE)
CWE-287 · Improper AuthenticationCVSS vector
AV:N/AC:M/Au:N/C:P/I:P/A:P
nvd-primary
Root cause
Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.
The bug in code
The whole CWE-287 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middlewareapp.post("/admin-api/config", updateConfig);Fixed
const admin = express.Router();admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);app.use("/admin", admin);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Authentication AbuseCAPEC-114Medium
- Authentication BypassCAPEC-115Medium
- Identity SpoofingCAPEC-151likelihood: Medium · Medium
- Fake the Source of DataCAPEC-194Medium
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Utilizing REST's Trust in the System Resource to Obtain Sensitive DataCAPEC-57likelihood: Medium · Very High
- Session HijackingCAPEC-593likelihood: High · Very High
- Token ImpersonationCAPEC-633Medium
ATT&CK techniques
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- rhn.redhat.com/errata/RHSA-2013-0561.html
- rhn.redhat.com/errata/RHSA-2013-0562.html
- secunia.com/advisories/52516
- bugzilla.redhat.com/show_bug.cgi?id=851355
- issues.apache.org/jira/browse/QPID-4631
Vendor advisories and official records. Exploit/PoC links are deliberately left out.