dbcve.org
AmqApplication · Redhat

CVE-2015-5183

HIGH · 7.5 CVSS v3.1 Published 2017-09-25
Fix available
A fix is available. Upgrade to 6.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Console: HTTPOnly and Secure attributes not set on cookies 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 confidence

The Red Hat AMQ Console does not set HTTPOnly and Secure flags on session cookies, allowing them to be accessed via JavaScript (enabling XSS-based session hijacking) and transmitted over unencrypted HTTP connections.

MitigationConfigure the AMQ web console or underlying servlet container to set HTTPOnly and Secure flags on all session cookies.

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
Affected:< 6.3
Jboss A MqApplication
Affected:= 7
Jboss Enterprise Web ServerApplication
Affected:= 1.0.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Red Hat AMQ version
    Run 'rpm -q redhat-amq' or check the product version through the AMQ console or installation directory. Compare against the affected versions: < 6.3 for Red Hat AMQ, = 7 for JBoss AMQ, = 1.0.0 for JBoss Enterprise Web Server.
    Affected if The installed version is lower than 6.3 for AMQ, equals 7 for JBoss AMQ, or equals 1.0.0 for JBoss Enterprise Web Server.
  2. Inspect session cookie headers
    Log into the AMQ web console and use browser developer tools (Application/Storage tab) to inspect the Set-Cookie header for the JSESSIONID cookie. Alternatively, capture a login response with curl -v and examine the Set-Cookie header.
    Affected if The JSESSIONID cookie does not contain 'HttpOnly' and 'Secure' flags in the Set-Cookie header.
  3. Verify HTTPOnly flag configuration
    Check the web.xml deployment descriptor for the AMQ console application (typically in /opt/amq/webconsole or similar path under the servlet container). Look for <session-config> <cookie-config> <http-only> element.
    Affected if The http-only element is missing, set to false, or the cookie-config element is not defined.
  4. Verify Secure flag configuration
    Check the same web.xml session-config cookie-config section for the <secure> element. Also verify the connector configuration in the servlet container (standalone.xml for JBoss) to ensure HTTPS is required.
    Affected if The secure element is missing, set to false, or the underlying connector is not configured to require SSL.

You are affected if your AMQ version falls within the affected ranges AND the JSESSIONID cookie lacks both HTTPOnly and Secure flags in its Set-Cookie header.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 6.3 or later
Fixed in 6.3
Interim mitigation

Configure the AMQ web console or underlying servlet container to set HTTPOnly and Secure flags on all session cookies.

Fix this in Amq Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-5183 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-5183 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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