AmqApplication · Redhat
CVE-2015-5182
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 · uneditedCross-site request forgery (CSRF) vulnerability in the jolokia API in A-MQ.
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 confidenceCross-site request forgery (CSRF) vulnerability in the jolokia API in Red Hat A-MQ. The flaw allows attackers to trick authenticated users into executing unintended requests against the jolokia JMX-over-HTTP bridge API, potentially leading to unauthorized management 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
all versionsCVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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.
-
Verify if jolokia endpoint is exposedInspect your A-MQ web server or proxy configuration to determine if the jolokia JMX-over-HTTP bridge API endpoint (typically accessible at /jolokia or similar paths) is publicly or internally accessibleAffected if The jolokia API endpoint is exposed without any CSRF protection mechanisms in place
-
Check for anti-CSRF token configurationReview the jolokia configuration files and web application security settings to determine whether anti-CSRF tokens are implemented for API requestsAffected if No anti-CSRF tokens are configured or enforced for jolokia API endpoints
-
Inspect SameSite cookie settingsExamine the cookie configuration for the jolokia session to verify if SameSite attributes are set on session cookiesAffected if SameSite cookie attributes are not defined or are set to None without proper CSRF safeguards
-
Check Origin/Referer header validationReview the web server or application configuration to determine if Origin or Referer headers are validated on requests to the jolokia APIAffected if Origin/Referer header validation is not enabled or enforced for jolokia requests
-
Confirm authenticated user accessDetermine whether users can authenticate to the jolokia API for JMX management operationsAffected if Authenticated users can access the jolokia API without CSRF protections in place
You are affected if the jolokia API endpoint is exposed and accessible to authenticated users without anti-CSRF tokens, SameSite cookies, or Origin/Referer validation protecting the requests.
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 dataImplement anti-CSRF tokens for jolokia API endpoints, enforce SameSite cookie attributes, and validate Origin/Referer headers on requests to prevent cross-site request forgery attacks.
Fix this in Amq
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-2015-5182 — 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-5182 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