Read the docs
TI-2018-12286 Aliases CVE-2018-17187GHSA-xvch-r4wf-h8w9

Improper certificate validation in Apache Qpid Proton-J

Priority LOW 37CWE-295Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
High
Impact type
Spoofing
Confidentiality · integrity · availability
High · High · None
Fix status
Partial Red Hat: 4 without a fix

Attack profile from CVSS 3.0 · NVD. Fix status from CNA, GitHub and Red Hat. Impact type from CWE-295.

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.

Why it matters now

EPSS 0.02539 85th percentileScored 2026-11-07
Fix Partial org.apache.qpid:proton-j (Maven): 0.30.0Red Hat: 4 without a fix

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
ApacheApache Qpid Proton-JApache Qpid Proton-J 0.3 to 0.29.0—No fix listedCNA
—org.apache.qpid:proton-j (Maven)0.3 to before 0.30.00.30.0Patch availableGHSA-xvch-r4wf-h8w9
  • Apache Qpid Proton-J VendorApache Affected Apache Qpid Proton-J 0.3 to 0.29.0 Fixed in — No fix listed CNA
  • org.apache.qpid:proton-j (Maven) Vendor— Affected 0.3 to before 0.30.0 Fixed in 0.30.0 Patch available GHSA-xvch-r4wf-h8w9

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:apache:qpid_proton-j:*:*:*:*:*:*:*:*0.3 – 0.29.0VulnerableApache
  • cpe:2.3:a:apache:qpid_proton-j:*:*:*:*:*:*:*:* Versions 0.3 – 0.29.0 Vulnerable ·Apache

Remediation

  • Fix · GHSA-xvch-r4wf-h8w9 org.apache.qpid:proton-j (Maven) Fixed in 0.30.0 Advisory →

Vendor assessments

Red Hat

Red Hat rating: Moderate. Red Hat's page for this CVE →

ProductStatusPlan or fix
Red Hat Enterprise MRG 3AffectedNo fix planned: Will not fix
Red Hat Fuse 7AffectedNo fix planned: Will not fix
Red Hat JBoss A-MQ 6AffectedNo fix planned: Out of support scope
Red Hat JBoss Fuse 6AffectedNo fix planned: Out of support scope
Not affected: 1 product
  • Red Hat OpenShift Application Runtimes

Timeline

  1. 2026-10-02 Threatist record created from CVE-2018-17187
  2. 2026-10-03 Alias added: GHSA-xvch-r4wf-h8w9

References

  • TI-2026-47091 Apache Qpid Proton-J: Unbounded type nesting can lead to pre-authentication stackoverflow CVSS 3.1HIGH 7.5
  • TI-2026-47090 Apache Qpid Proton-J: Type size/count handling can lead to excessive allocation pre-authentication CVSS 3.1HIGH 7.5
  • TI-2026-47085 Apache Qpid Proton-J: Unbounded symbol value caching can lead to pre-authentication resource exhaustion CVSS 3.1HIGH 7.5
  • TI-2026-47094 Apache Qpid Proton-J: Unable to govern the maximum number of transfer frames per incoming delivery CVSS 3.1MEDIUM 6.5
  • TI-2026-47093 Apache Qpid Proton-J: Unbounded disposition range handling can lead to denial of service CVSS 3.1MEDIUM 6.5
  • TI-2026-47092 Apache Qpid Proton-J: Incoming session flow control window can be exceeded CVSS 3.1MEDIUM 6.5

Sources