Linux Distros Unpatched Vulnerability : CVE-2016-6810

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - In Apache ActiveMQ 5.x before 5.14.2, an instance of a cross-site scripting vulnerability was identified to be present in the web based administration console...

K55444705: Apache ActiveMQ vulnerability CVE-2016-6810

Security Advisory Description In Apache ActiveMQ 5.x before 5.14.2, an instance of a cross-site scripting vulnerability was identified to be present in the web based administration console. The root cause of this issue is improper user data output validation. CVE-2016-6810 Impact This vulnerabili...

at.chrl:chrl-jms (=1.1.0), at.researchstudio.sat:won-core (>=0.2 <=0.9) +527 more potentially affected by CVE-2016-6810 via org.apache.activemq:activemq-client (>=5.10.0 <=5.14.1)

org.apache.activemq:activemq-client MAVEN version =5.10.0, =0.2, =0.3, =0.2, =0.2, =0.3, =0.3, =0.3, =0.3, =0.3, =0.2, =0.3, =0.3, =0.6 - at.researchstudio.sat:won-owner =0.3 - at.researchstudio.sat:won-owner-webapp =0.3 and more Source cves: CVE-2016-6810 Source advisory: OSV:GHSA-5JG4-P78R-P5J3...

Security Bulletin: Vulnerability in Apache ActiveMQ affects IBM Control Center (CVE-2016-6810)

Summary Vulnerability in Apache ActiveMQ affects IBM Control Center. Vulnerability Details CVEID: CVE-2016-6810 DESCRIPTION: Apache ActiveMQ is vulnerable to cross-site scripting, caused by improper validation of user-supplied input. A remote attacker could exploit this vulnerability in a...

Apache Active MQ 5.14.1 XSS Vulnerability - Linux

Apache Active MQ 5.x before 5.14.1 is prone to an authenticated XSS vulnerability. SPDX-FileCopyrightText: 2018 Greenbone AG Some text descriptions might be excerpted from a referenced sources, and are Copyright C by the respective right holders. SPDX-License-Identifier: GPL-2.0-only if descripti...

CVE-2016-6810

In Apache ActiveMQ 5.x before 5.14.2, an instance of a cross-site scripting vulnerability was identified to be present in the web based administration console. The root cause of this issue is improper user data output validation...