CVE-2018-17187

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.

Link	Resource
https://qpid.apache.org/cves/CVE-2018-17187.html	Mitigation Vendor Advisory
https://mail-archives.apache.org/mod_mbox/qpid-users/201811.mbox/%3CCAFitrpQSV73Vz7rJYfLJK7gvEymZSCR5ooWUeU8j4jzRydk-eg%40mail.gmail.com%3E	Mitigation Mailing List
https://issues.apache.org/jira/browse/PROTON-1962	Vendor Advisory
http://www.securityfocus.com/bid/105935	Third Party Advisory VDB Entry

Configuration 1

cpe:2.3:a:apache:qpid_proton-j:*:*:*:*:*:*:*:*

---

Published : 2018-11-13 03:29

Updated : 2019-01-31 07:10

---

NVD link : CVE-2018-17187

Mitre link : CVE-2018-17187

No products.

CWE-295

Improper Certificate Validation