AmqApplication · Redhat
CVE-2015-5184
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 · uneditedConsole: CORS headers set to allow all in Red Hat AMQ.
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 confidenceThe Red Hat AMQ console incorrectly sets CORS (Cross-Origin Resource Sharing) headers to allow requests from any origin (*), enabling malicious websites to make authenticated cross-origin requests to the AMQ console API and potentially exfiltrate data or perform unauthorized operations.
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
AmqApplication
< 6.2.1
Jboss Enterprise Web ServerApplication
= 1.0.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 AMQ console versionLocate the Red Hat AMQ installation directory and check the version file or JAR manifest, typically found in the bin or lib directory, or query the running process for version informationAffected if The installed version is lower than 6.2.1
-
Check JBoss Enterprise Web Server versionQuery the JBoss Enterprise Web Server installation for its version number using the version scripts or by inspecting installed package informationAffected if The installed version equals 1.0.0 exactly
-
Inspect CORS configuration in web connectorExamine the web connector configuration file (such as jetty.xml, undertow.xml, or similar) used by the AMQ console for CORS-related settings, specifically looking for Access-Control-Allow-Origin directivesAffected if The Access-Control-Allow-Origin header is set to '*' or is not explicitly restricted to specific trusted origins
-
Inspect proxy configuration for CORS headersIf a web proxy or load balancer sits in front of the AMQ console, review its configuration for CORS headers that may be propagating the wildcard origin allowanceAffected if The proxy configuration allows '*' for Access-Control-Allow-Origin without restricting to specific origins
-
Test CORS response headersSend an HTTP request to the AMQ console API endpoint with an Origin header set to an arbitrary domain (such as http://evil.com) and inspect the response headers for Access-Control-Allow-OriginAffected if The response contains Access-Control-Allow-Origin: * or echoes back the arbitrary origin provided in the request
A user is affected if they run Red Hat AMQ below version 6.2.1 or JBoss Enterprise Web Server version 1.0.0, AND the CORS configuration permits requests from any origin (*).
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 data6.2.1
Configure the AMQ console to only accept CORS requests from specific, trusted origins rather than allowing all origins, typically by modifying the web connector or proxy configuration.
Fix this in Amq
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5184 — 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-2015-5184 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