VDB

CVE-2018-17187

CVE-2018-17187 PUBLISHED CVSS 7.400000095367432 HIGH

Improper Certificate Validation in proton-j

Reported by apache · Published November 13, 2018

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.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
qpid_proton-japache0.29.0

Risk scores

CVSS 3.0
7.400000095367432
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected products

VendorProductVersions
Apache Software FoundationApache Qpid Proton-JApache Qpid Proton-J 0.3 to 0.29.0
Mavenorg.apache.qpid:proton-j0.3
Apache Software FoundationApache Qpid Proton-J0.3

Timeline

  • Nov 13, 2018 CVE Published
  • Apr 14, 2021 EPSS Score (30 in total, the first dated here)
  • Oct 24, 2025 CVE Updated
  • Mar 17, 2026 Security Advisory
  • Sep 23, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2018-17187
vulnetix vdb fixes CVE-2018-17187

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2018-17187/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›