What is the severity of CVE-2016-4467?

CVE-2016-4467 has been classified as a medium severity vulnerability.

How do I fix CVE-2016-4467?

To fix CVE-2016-4467, upgrade the Apache Qpid Proton library to version 0.13.1 or later.

What versions of Apache Qpid Proton are affected by CVE-2016-4467?

CVE-2016-4467 affects Apache Qpid Proton versions 0.8.0 through 0.13.0.

What type of attack does CVE-2016-4467 expose users to?

CVE-2016-4467 exposes users to potential man-in-the-middle attacks due to improper hostname verification.

Is there a known workaround for CVE-2016-4467?

There is no officially recommended workaround for CVE-2016-4467; upgrading is the best course of action.

Vulnerability/
CVE-2016-4467

medium

5.9

CWE

295

2/5/2017

6/8/2024

CVE-2016-4467

First published: Tue May 02 2017(Updated: )

The C client and C-based client bindings in the Apache Qpid Proton library before 0.13.1 on Windows do not properly verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate when using the SChannel-based security layer, which allows man-in-the-middle attackers to spoof servers via an arbitrary valid certificate.

Credit: secalert@redhat.com

Affected Software	Affected Version	How to fix
Apache Qpid Proton	=0.8.0
Apache Qpid Proton	=0.9.0
Apache Qpid Proton	=0.9.1
Apache Qpid Proton	=0.10.0
Apache Qpid Proton	=0.11.0
Apache Qpid Proton	=0.11.1
Apache Qpid Proton	=0.12.0
Apache Qpid Proton	=0.12.1
Apache Qpid Proton	=0.12.2
Apache Qpid Proton	=0.13.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-4467?
CVE-2016-4467 has been classified as a medium severity vulnerability.
How do I fix CVE-2016-4467?
To fix CVE-2016-4467, upgrade the Apache Qpid Proton library to version 0.13.1 or later.
What versions of Apache Qpid Proton are affected by CVE-2016-4467?
CVE-2016-4467 affects Apache Qpid Proton versions 0.8.0 through 0.13.0.
What type of attack does CVE-2016-4467 expose users to?
CVE-2016-4467 exposes users to potential man-in-the-middle attacks due to improper hostname verification.
Is there a known workaround for CVE-2016-4467?
There is no officially recommended workaround for CVE-2016-4467; upgrading is the best course of action.

collector/nvd-index
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/weakness
agent/severity
agent/references
agent/last-modified-date
agent/tags
agent/description
agent/first-publish-date
agent/author
agent/event
agent/source
vendor/apache
canonical/apache qpid proton
version/apache qpid proton/0.8.0
version/apache qpid proton/0.9.0
version/apache qpid proton/0.9.1
version/apache qpid proton/0.10.0
version/apache qpid proton/0.11.0
version/apache qpid proton/0.11.1
version/apache qpid proton/0.12.0
version/apache qpid proton/0.12.1
version/apache qpid proton/0.12.2
version/apache qpid proton/0.13.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2016-4467?
CVE-2016-4467 has been classified as a medium severity vulnerability.
How do I fix CVE-2016-4467?
To fix CVE-2016-4467, upgrade the Apache Qpid Proton library to version 0.13.1 or later.
What versions of Apache Qpid Proton are affected by CVE-2016-4467?
CVE-2016-4467 affects Apache Qpid Proton versions 0.8.0 through 0.13.0.
What type of attack does CVE-2016-4467 expose users to?
CVE-2016-4467 exposes users to potential man-in-the-middle attacks due to improper hostname verification.
Is there a known workaround for CVE-2016-4467?
There is no officially recommended workaround for CVE-2016-4467; upgrading is the best course of action.