ActivemqApplication · Apache
CVE-2016-0734
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 · uneditedThe web-based administration console in Apache ActiveMQ 5.x before 5.13.2 does not send an X-Frame-Options HTTP header, which makes it easier for remote attackers to conduct clickjacking attacks via a crafted web page that contains a (1) FRAME or (2) IFRAME element.
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 · high confidenceThe Apache ActiveMQ 5.x web-based administration console before version 5.13.2 does not include the X-Frame-Options HTTP header in its responses. This allows an attacker to embed the admin console in an iframe on a malicious webpage (clickjacking), tricking authenticated administrators into performing unintended actions such as sending messages or managing destinations.
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
ActivemqApplication
= 5.0.0= 5.1.0= 5.2.0= 5.3.0= 5.3.1= 5.3.2= 5.4.0= 5.4.1= 5.4.2= 5.4.3= 5.5.0= 5.5.1CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 installed ActiveMQ versionLocate the ActiveMQ installation directory and check the version. Common methods: look for a VERSION file, check the README or CHANGES file, or inspect the manifest of the main activemq.jar file in the lib folder.Affected if The installed version is any of: 5.0.0, 5.1.0, 5.2.0, 5.3.0, 5.3.1, 5.3.2, 5.4.0, 5.4.1, 5.4.2, 5.4.3, 5.5.0, or 5.5.1.
-
Verify web admin console is enabledCheck if the ActiveMQ web-based administration console is accessible. Common ports are 8161 (default Jetty port). Attempt to access http://localhost:8161/admin/ or the root URL of the web console.Affected if The web admin console is accessible and responding to HTTP requests.
-
Inspect HTTP response for X-Frame-Options headerSend an HTTP request to the admin console endpoint and examine the response headers. Use a command such as: curl -I http://localhost:8161/admin/ (or the appropriate URL). Look for the X-Frame-Options header in the response.Affected if The response headers from the admin console do NOT contain an X-Frame-Options header, or the header value is missing.
You are affected if you are running any of the listed affected versions (5.0.0 through 5.5.1), the web admin console is enabled and accessible, and the HTTP responses from the admin console lack the X-Frame-Options security header.
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 dataConfigure the embedded Jetty web server to send X-Frame-Options: DENY or SAMEORIGIN header on all admin console responses, or implement Content-Security-Policy with frame-ancestors directive as a modern alternative.
Fix this in Activemq
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-0734 — 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-2016-0734 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