Apache Qpid up to 0.13.0 on Windows Proton Library Certificate certificate validation

Summaryinfo

A vulnerability labeled as critical has been found in Apache Qpid up to 0.13.0 on Windows. Affected is an unknown function of the component Proton Library. The manipulation as part of Certificate results in certificate validation. This vulnerability is cataloged as CVE-2016-4467. The attack may be launched remotely. There is no exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in Apache Qpid up to 0.13.0 on Windows. It has been classified as critical. Affected is an unknown part of the component Proton Library. The manipulation as part of a Certificate leads to a certificate validation vulnerability. CWE is classifying the issue as CWE-295. The product does not validate, or incorrectly validates, a certificate. This is going to have an impact on confidentiality, integrity, and availability.

The weakness was shared 07/15/2016 as confirmed release notes (Website). The advisory is shared for download at qpid.apache.org. This vulnerability is traded as CVE-2016-4467 since 05/02/2016. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1587.003. The advisory points out:

Messaging applications using the Proton C library to provide SSL/TLS authentication on Windows can falsely authenticate a server whose name does not match the server name in the connection specifier. Proton C bindings are affected to a greater or lesser degree depending on how they use the underlying Proton C library. In Proton C, this can only happen if PN_SSL_VERIFY_PEER_NAME has been specified as the verification mode and pn_ssl_set_peer_hostname() has not been called at all or has been called with a NULL value for a particular pn_ssl_t object. In the Proton C++ binding, this will always happen unless the application has separately specified a virtual_host name for an SSL/TLS connection. In the Proton Python and Ruby bindings, this will only happen if the application has separately specified a NULL virtual_host name for an SSL/TLS connection after creating the connection but before the authentication step.

Upgrading to version 0.13.1 eliminates this vulnerability. The release notes contains the following remark:

Proton release 0.13.1 resolves this issue in the SChannel-based security layer by obtaining a default non-NULL peer hostname from the associated connection address when initialized and by always failing hostname verification if PN_SSL_VERIFY_PEER_NAME has been specified along with a NULL peer hostname. This resolution matches the associated behaviour of the OpenSSL-based security layer.

The vulnerability is also documented in the databases at SecurityFocus (BID 91788†) and SecurityTracker (ID 1036316†). Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• Apache

Name

• Qpid

Version

• 0.1
• 0.2
• 0.3
• 0.4
• 0.5
• 0.6
• 0.7
• 0.8
• 0.9
• 0.10
• 0.11
• 0.12
• 0.13.0

License

• open-source

Website

• Vendor: https://www.apache.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion