SUSE-SU-2018:2699-1 Security update for tomcat

This update for tomcat to 8.0.53 fixes the following issues: Security issue fixed: - CVE-2018-1336: An improper handing of overflow in the UTF-8 decoder with supplementary characters could have lead to an infinite loop in the decoder causing a Denial of Service bsc1102400. - CVE-2018-8034: The ho...

Design/Logic Flaw

D-Link DIR-600M devices allow XSS via the Hostname and Username fields in the Dynamic DNS Configuration page...

Man-in-the-Middle (MitM)

spring-rabbit is vulnerable to man-in-the-middle attacks. The Spring RabbitMQ Java client does not perform SSL hostname validation and accepts SSL certificates as long as they are trusted. This allows attackers to perform man-in-the-middle attacks between the RabbitMQ Java client and server...

PT-2018-13644

Name of the Vulnerable Software and Affected Versions D-Link DIR-600M affected versions not specified Description The issue allows for cross-site scripting XSS attacks through the Hostname and Username fields in the Dynamic DNS Configuration page. This can potentially lead to malicious script...

CVE-2018-16605: Improper Neutralization of Input During Web Page Generation

D-Link DIR-600M devices allow XSS via the Hostname and Username fields in the Dynamic DNS Configuration page...

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-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-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-11775

CVE-2018-11775 affects the Apache ActiveMQ Client, where TLS hostname verification was missing prior to version 5.15.6, enabling potential MITM between a Java application and the ActiveMQ server. The issue is stated as now being enabled by default and is addressed by upgrading the ActiveMQ client...

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-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-2016-7075

It was found that Kubernetes as used by Openshift Enterprise 3 did not correctly validate X.509 client intermediate certificate host name fields. An attacker could use this flaw to bypass authentication requirements by using a specially crafted X.509 certificate...

PT-2018-4981 · Linux Foundation +1 · Kubernetes +1

Name of the Vulnerable Software and Affected Versions: Openshift Enterprise 3 Description: A flaw was found in the validation of X.509 client intermediate certificate host name fields in Kubernetes as used by Openshift Enterprise. This could allow an attacker to bypass authentication requirements...

CVE-2018-11775: Improper Certificate Validation

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...

PT-2018-2280 · Apache +2 · Apache Activemq +2

Name of the Vulnerable Software and Affected Versions: Apache ActiveMQ versions prior to 5.15.6 Description: The issue is related to errors in security settings and the absence of TLS hostname verification in the Apache ActiveMQ broker. This could allow a remote attacker to implement a...

apache-cxf: TLS hostname verification does not work correctly with com.sun.net.ssl.*

It was discovered that when Apache CXF is configured to use the system property com.sun.net.ssl.internal.www.protocol ,it uses reflection to make the HostnameVerifier work with old com.sun.net.ssl.HostnameVerifier interface. Although the CXF implementation throws an exception, which is caught in...