Homepage

Improper Certificate Validation Affecting qpid-proton package, versions <0.22.0-1

Severity

 Recommended
0.0
high
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
2.54% (83rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ECHOLATEST-QPIDPROTON-18533403
  • published5 Aug 2026
  • disclosed13 Nov 2018
Report a new vulnerability Found a mistake?

Introduced: 13 Nov 2018

CVE-2018-17187  (opens in a new tab)
CWE-295  (opens in a new tab)

How to fix?

Upgrade Echo:latest qpid-proton to version 0.22.0-1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream qpid-proton package and not the qpid-proton package as distributed by Echo. See How to fix? for Echo:latest relevant fixed versions and status.

The Apache Qpid Proton-J transport includes an optional wrapper layer to perform TLS, enabled by use of the 'transport.ssl(...)' 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.