at.chrl:chrl-jms (=1.1.0), at.researchstudio.sat:won-core (>=0.2 <=0.9) +1019 more potentially affected by CVE-2019-0222 via org.apache.activemq:activemq-client (>=5.10.0 <=5.15.8)

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-2019-0222 Source advisory: OSV:GHSA-JPV3-G4CC-6VFX...

GHSA-JPV3-G4CC-6VFX Improper Control of Generation of Code ('Code Injection') in org.apache.activemq:activemq-client

In Apache ActiveMQ 5.0.0 - 5.15.8, unmarshalling corrupt MQTT frame can lead to broker Out of Memory exception making it unresponsive...

GHSA-M9W8-V359-9FFR Improper Certificate Validation in Apache activemq-client

TLS hostname verification when using the Apache ActiveMQ Client before 5.15.6 was missing which could make the client vulnerable to a MITM attack between a Java application using the ActiveMQ client and the ActiveMQ server. This is now enabled by default...

Improper Certificate Validation in Apache activemq-client

TLS hostname verification when using the Apache ActiveMQ Client before 5.15.6 was missing which could make the client vulnerable to a MITM attack between a Java application using the ActiveMQ client and the ActiveMQ server. This is now enabled by default...

Man-in-the-Middle (MitM)

activemq-client is vulnerable to man-in-the-middle MitM attacks. The vulnerability exists due to the lack of TLS hostname verification which would potentially allow the client to be vulnerable to MitM attacks...

Apache ActiveMQ Security Restriction Bypass Vulnerability

Apache ActiveMQ Client is the United States Apache Apache Software Foundation developed a set of open-source messaging middleware client program , which supports Java messaging services , clustering , Spring Framework and so on. Apache ActiveMQ Client 5.15.6 before the version of a security...

Default credentials

TLS hostname verification when using the Apache ActiveMQ Client before 5.15.6 was missing which could make the client vulnerable to a MITM attack between a Java application using the ActiveMQ client and the ActiveMQ server. This is now enabled by default...

UBUNTU-CVE-2018-11775

TLS hostname verification when using the Apache ActiveMQ Client before 5.15.6 was missing which could make the client vulnerable to a MITM attack between a Java application using the ActiveMQ client and the ActiveMQ server. This is now enabled by default...

DEBIAN-CVE-2018-11775

TLS hostname verification when using the Apache ActiveMQ Client before 5.15.6 was missing which could make the client vulnerable to a MITM attack between a Java application using the ActiveMQ client and the ActiveMQ server. This is now enabled by default...

CVE-2018-1310

Apache NiFi JMS Deserialization issue because of ActiveMQ client vulnerability. Malicious JMS content could cause denial of service. See ActiveMQ CVE-2015-5254 announcement for more information. The fix to upgrade the activemq-client library to 5.15.3 was applied on the Apache NiFi 1.6.0 release...

Deserialization of untrusted data

Apache NiFi JMS Deserialization issue because of ActiveMQ client vulnerability. Malicious JMS content could cause denial of service. See ActiveMQ CVE-2015-5254 announcement for more information. The fix to upgrade the activemq-client library to 5.15.3 was applied on the Apache NiFi 1.6.0 release...

Information Disclosure

activemq-client is vulnerable to information disclosure. When using the OpenWire protocol, sensitive information such as the operating system is exposed as plaintext. Using this knowledge, attackers can find existing exploits to make attacking an application easier...

Denial Of Service (DoS)

activemq-client is vulnerable to denial of service DoS attacks. The vulnerability is possible because it exposes a remote shutdown command in the ActiveMQConnection class, allowing the attacker to use it to launch the attack...