Skip to content
Fencer Vulns
high 7.4

CVE-2018-17187 json

Improper Certificate Validation in proton-j

published 2018-11-13 7 y ago modified 2026-06-17 4 mo ago also GHSA-xvch-r4wf-h8w9 , EUVD-2018-0790

cvss
7.4
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.5%
EPSS 2.5% chance of exploitation in 30 days, percentile 85%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.apache.qpid:proton-j 0.30.0
  • qpid-proton Debian 14, Debian 13, Debian 12 0.22.0-1

debian advisories DEBIAN-CVE-2018-17187

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-17187 updated cvss 6.8

qpid-proton-java: Hostname verification mode not implemented in transport TLS wrapper

  • Red Hat Enterprise MRG 3 qpid-proton-java Red Hat Fuse 7 proton-j
    affected: no fix planned “Will not fix”
  • Red Hat JBoss A-MQ 6 proton-j Red Hat JBoss Fuse 6 proton-j
    affected: no fix planned “Out of support scope”
  • Red Hat OpenShift Application Runtimes proton-j
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.54% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.0 7.4 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
NVD 2.0 5.8 AV:N/AC:M/Au:N/C:P/I:P/A:N
GitHub 3.0 7.4 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
maven org.apache.qpid:proton-j
>=0.3, <0.30.0
0.30.0

Affected products

  • Apache Software Foundation Apache Qpid Proton-J

Classification

Weakness
  • CWE-295 Improper Certificate Validation

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.