https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 08:36:00 +0000 https://cve.radiocsirt.org/vuln/bdu:2019-01322 bdu:2019-01322 https://cve.radiocsirt.org/vuln/bdu:2019-01322 https://cve.radiocsirt.org/vuln/euvd-2026-68568 EUVD-2026-68568 https://cve.radiocsirt.org/vuln/euvd-2026-68568 https://cve.radiocsirt.org/vuln/fkie_cve-2018-17187 <p>The Apache Qpid Proton-J transport includes an optional wrapper layer to perform TLS, enabled by use of the &#39;transport.ssl(...)&#39; methods. Unless a verification mode was explicitly configured, client and server modes previously defaulted as documented to not verifying a peer certificate, with options to configure this explicitly or select a certificate verification mode with or without hostname verification being performed. The latter hostname verifying mode was not implemented in Apache Qpid Proton-J versions 0.3 to 0.29.0, with attempts to use it resulting in an exception. This left only the option to verify the certificate is trusted, leaving such a client vulnerable to Man In The Middle (MITM) attack. Uses of the Proton-J protocol engine which do not utilise the optional transport TLS wrapper are not impacted, e.g. usage within Qpid JMS. Uses of Proton-J utilising the optional transport TLS wrapper layer that wish to enable hostname verification must be upgraded to version 0.30.0 or later and utilise the VerifyMode#VERIFY_PEER_NAME configuration, which is now the default for client mode usage unless configured otherwise.</p> <p>The Apache Qpid Proton-J transport includes an optional wrapper layer to perform TLS, enabled by use of the &#39;transport.ssl(...)&#39; methods. Unless a verification mode was explicitly configured, client and server modes previously defaulted as documented to not verifying a peer certificate, with options to configure this explicitly or select a certificate verification mode with or without hostname verification being performed. The latter hostname verifying mode was not implemented in Apache Qpid Proton-J versions 0.3 to 0.29.0, with attempts to use it resulting in an exception. This left only the option to verify the certificate is trusted, leaving such a client vulnerable to Man In The Middle (MITM) attack. Uses of the Proton-J protocol engine which do not utilise the optional transport TLS wrapper are not impacted, e.g. usage within Qpid JMS. Uses of Proton-J utilising the optional transport TLS wrapper layer that wish to enable hostname verification must be upgraded to version 0.30.0 or later and utilise the VerifyMode#VERIFY_PEER_NAME configuration, which is now the default for client mode usage unless configured otherwise.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2018-17187 https://cve.radiocsirt.org/vuln/ghsa-xvch-r4wf-h8w9 <p><strong>Affected:</strong> Maven: org.apache.qpid:proton-j</p> <p>The Apache Qpid Proton-J transport includes an optional wrapper layer to perform TLS, enabled by use of the &#39;transport.ssl(...)&#39; methods. Unless a verification mode was explicitly configured, client and server modes previously defaulted as documented to not verifying a peer certificate, with options to configure this explicitly or select a certificate verification mode with or without hostname verification being performed. The latter hostname verifying mode was not implemented in Apache Qpid Proton-J versions 0.3 to 0.29.0, with attempts to use it resulting in an exception. This left only the option to verify the certificate is trusted, leaving such a client vulnerable to Man In The Middle (MITM) attack. Uses of the Proton-J protocol engine which do not utilise the optional transport TLS wrapper are not impacted, e.g. usage within Qpid JMS. Uses of Proton-J utilising the optional transport TLS wrapper layer that wish to enable hostname verification must be upgraded to version 0.30.0 or later and utilise the VerifyMode#VERIFY_PEER_NAME configuration, which is now the default for client mode usage unless configured otherwise.</p> <p><strong>Affected:</strong> Maven: org.apache.qpid:proton-j</p> <p>The Apache Qpid Proton-J transport includes an optional wrapper layer to perform TLS, enabled by use of the &#39;transport.ssl(...)&#39; methods. Unless a verification mode was explicitly configured, client and server modes previously defaulted as documented to not verifying a peer certificate, with options to configure this explicitly or select a certificate verification mode with or without hostname verification being performed. The latter hostname verifying mode was not implemented in Apache Qpid Proton-J versions 0.3 to 0.29.0, with attempts to use it resulting in an exception. This left only the option to verify the certificate is trusted, leaving such a client vulnerable to Man In The Middle (MITM) attack. Uses of the Proton-J protocol engine which do not utilise the optional transport TLS wrapper are not impacted, e.g. usage within Qpid JMS. Uses of Proton-J utilising the optional transport TLS wrapper layer that wish to enable hostname verification must be upgraded to version 0.30.0 or later and utilise the VerifyMode#VERIFY_PEER_NAME configuration, which is now the default for client mode usage unless configured otherwise.</p> https://cve.radiocsirt.org/vuln/ghsa-xvch-r4wf-h8w9 https://cve.radiocsirt.org/vuln/gsd-2018-17187 gsd-2018-17187 https://cve.radiocsirt.org/vuln/gsd-2018-17187 https://cve.radiocsirt.org/vuln/ubuntu-cve-2018-17187 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: qpid-proton, Ubuntu:18.04:LTS: qpid-proton</p> <p>The Apache Qpid Proton-J transport includes an optional wrapper layer to perform TLS, enabled by use of the &#39;transport.ssl(...)&#39; methods. Unless a verification mode was explicitly configured, client and server modes previously defaulted as documented to not verifying a peer certificate, with options to configure this explicitly or select a certificate verification mode with or without hostname verification being performed. The latter hostname verifying mode was not implemented in Apache Qpid Proton-J versions 0.3 to 0.29.0, with attempts to use it resulting in an exception. This left only the option to verify the certificate is trusted, leaving such a client vulnerable to Man In The Middle (MITM) attack. Uses of the Proton-J protocol engine which do not utilise the optional transport TLS wrapper are not impacted, e.g. usage within Qpid JMS. Uses of Proton-J utilising the optional transport TLS wrapper layer that wish to enable hostname verification must be upgraded to version 0.30.0 or later and utilise the VerifyMode#VERIFY_PEER_NAME configuration, which is now the default for client mode usage unless configured otherwise.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: qpid-proton, Ubuntu:18.04:LTS: qpid-proton</p> <p>The Apache Qpid Proton-J transport includes an optional wrapper layer to perform TLS, enabled by use of the &#39;transport.ssl(...)&#39; methods. Unless a verification mode was explicitly configured, client and server modes previously defaulted as documented to not verifying a peer certificate, with options to configure this explicitly or select a certificate verification mode with or without hostname verification being performed. The latter hostname verifying mode was not implemented in Apache Qpid Proton-J versions 0.3 to 0.29.0, with attempts to use it resulting in an exception. This left only the option to verify the certificate is trusted, leaving such a client vulnerable to Man In The Middle (MITM) attack. Uses of the Proton-J protocol engine which do not utilise the optional transport TLS wrapper are not impacted, e.g. usage within Qpid JMS. Uses of Proton-J utilising the optional transport TLS wrapper layer that wish to enable hostname verification must be upgraded to version 0.30.0 or later and utilise the VerifyMode#VERIFY_PEER_NAME configuration, which is now the default for client mode usage unless configured otherwise.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2018-17187