CVE-2018-17187
published 2018-11-13CVE-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…
PriorityP341high7.4CVSS 3.0
AVNACHPRNUINSUCHIHAN
EPSS
2.54%
83.8th percentile
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.
Affected
3 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| apache | qpid_proton-j | 0.3 – 0.29.0 | — |
| apache_software_foundation | apache_qpid_proton-j | — | — |
| debian | qpid-proton | < qpid-proton 0.22.0-1 (bookworm) | qpid-proton 0.22.0-1 (bookworm) |
CVSS provenance
nvdv3.07.4HIGHCVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
nvdv2.05.8MEDIUMAV:N/AC:M/Au:N/C:P/I:P/A:N
osv7.4HIGH
vendor_debian7.4LOW
vendor_redhat7.4HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
qpid-proton-java: Hostname verification mode not implemented in transport TLS wrapper
vendor_redhat·2018-11-12·CVSS 7.4
CVE-2018-17187 [HIGH] CWE-295 qpid-proton-java: Hostname verification mode not implemented in transport TLS wrapper
qpid-proton-java: Hostname verification mode not implemented in transport TLS wrapper
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.
Debian
CVE-2018-17187: qpid-proton - The Apache Qpid Proton-J transport includes an optional wrapper layer to perform...
vendor_debian·2018·CVSS 7.4
CVE-2018-17187 [HIGH] CVE-2018-17187: qpid-proton - The Apache Qpid Proton-J transport includes an optional wrapper layer to perform...
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 w
GHSA
Improper Certificate Validation in proton-j
ghsa·2018-11-21
CVE-2018-17187 [HIGH] CWE-295 Improper Certificate Validation in proton-j
Improper Certificate Validation in proton-j
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 whic
OSV
Improper Certificate Validation in proton-j
osv·2018-11-21
CVE-2018-17187 [HIGH] Improper Certificate Validation in proton-j
Improper Certificate Validation in proton-j
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 whic
OSV
CVE-2018-17187: The Apache Qpid Proton-J transport includes an optional wrapper layer to perform TLS, enabled by use of the 'transport
osv·2018-11-13·CVSS 7.4
CVE-2018-17187 [HIGH] CVE-2018-17187: The Apache Qpid Proton-J transport includes an optional wrapper layer to perform TLS, enabled by use of the 'transport
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 w
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2018-17187 qpid-proton-java: Hostname verification mode not implemented in transport TLS wrapper [fedora-all]
bugzilla·2018-11-21·CVSS 7.4
CVE-2018-17187 [HIGH] CVE-2018-17187 qpid-proton-java: Hostname verification mode not implemented in transport TLS wrapper [fedora-all]
CVE-2018-17187 qpid-proton-java: Hostname verification mode not implemented in transport TLS wrapper [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue
Bugzilla
CVE-2018-17187 qpid-proton-java: Hostname verification mode not implemented in transport TLS wrapper
bugzilla·2018-11-21·CVSS 7.4
CVE-2018-17187 [HIGH] CVE-2018-17187 qpid-proton-java: Hostname verification mode not implemented in transport TLS wrapper
CVE-2018-17187 qpid-proton-java: Hostname verification mode not implemented in transport TLS wrapper
The 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 previously implemented, 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
http://www.securityfocus.com/bid/105935https://issues.apache.org/jira/browse/PROTON-1962https://mail-archives.apache.org/mod_mbox/qpid-users/201811.mbox/%3CCAFitrpQSV73Vz7rJYfLJK7gvEymZSCR5ooWUeU8j4jzRydk-eg%40mail.gmail.com%3Ehttps://qpid.apache.org/cves/CVE-2018-17187.htmlhttp://www.securityfocus.com/bid/105935https://issues.apache.org/jira/browse/PROTON-1962https://mail-archives.apache.org/mod_mbox/qpid-users/201811.mbox/%3CCAFitrpQSV73Vz7rJYfLJK7gvEymZSCR5ooWUeU8j4jzRydk-eg%40mail.gmail.com%3Ehttps://qpid.apache.org/cves/CVE-2018-17187.html
2018-11-13
Published