What is the severity of CVE-2012-5786?

CVE-2012-5786 is considered a moderate severity vulnerability due to improper hostname verification in Apache CXF.

How do I fix CVE-2012-5786?

To fix CVE-2012-5786, upgrade Apache CXF to version 2.7.0 or later.

What types of attacks can exploit CVE-2012-5786?

CVE-2012-5786 can be exploited by man-in-the-middle attacks due to the lack of hostname verification.

Which versions of Apache CXF are affected by CVE-2012-5786?

Apache CXF versions up to and including 2.6.17 are affected by CVE-2012-5786.

Is CVE-2012-5786 a protocol-specific vulnerability?

Yes, CVE-2012-5786 specifically affects the HTTPS implementation in Apache CXF.

Vulnerability/
CVE-2012-5786

medium

5.8

CWE

4/11/2012

6/8/2024

CVE-2012-5786: Input Validation

First published: Sun Nov 04 2012(Updated: )

** DISPUTED ** The wsdl_first_https sample code in distribution/src/main/release/samples/wsdl_first_https/src/main/ in Apache CXF before 2.7.0 does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate. NOTE: The vendor states that the sample had specifically used a flag to bypass the DN check.

Credit: cve@mitre.org cve@mitre.org

Affected Software	Affected Version	How to fix
Apache CXF	<=2.6.17
	<=2.6.17

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2012-5786?
CVE-2012-5786 is considered a moderate severity vulnerability due to improper hostname verification in Apache CXF.
How do I fix CVE-2012-5786?
To fix CVE-2012-5786, upgrade Apache CXF to version 2.7.0 or later.
What types of attacks can exploit CVE-2012-5786?
CVE-2012-5786 can be exploited by man-in-the-middle attacks due to the lack of hostname verification.
Which versions of Apache CXF are affected by CVE-2012-5786?
Apache CXF versions up to and including 2.6.17 are affected by CVE-2012-5786.
Is CVE-2012-5786 a protocol-specific vulnerability?
Yes, CVE-2012-5786 specifically affects the HTTPS implementation in Apache CXF.

collector/nvd-index
agent/references
agent/type
agent/severity
agent/weakness
agent/author
agent/status
agent/softwarecombine
agent/description
agent/tags
agent/first-publish-date
agent/event
collector/mitre-cve
source/MITRE
collector/nvd-api
source/NVD
agent/software-canonical-lookup
agent/last-modified-date
agent/source
status/disputed
vendor/apache
canonical/apache cxf
version/apache cxf/2.6.17

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-2012-5786?
CVE-2012-5786 is considered a moderate severity vulnerability due to improper hostname verification in Apache CXF.
How do I fix CVE-2012-5786?
To fix CVE-2012-5786, upgrade Apache CXF to version 2.7.0 or later.
What types of attacks can exploit CVE-2012-5786?
CVE-2012-5786 can be exploited by man-in-the-middle attacks due to the lack of hostname verification.
Which versions of Apache CXF are affected by CVE-2012-5786?
Apache CXF versions up to and including 2.6.17 are affected by CVE-2012-5786.
Is CVE-2012-5786 a protocol-specific vulnerability?
Yes, CVE-2012-5786 specifically affects the HTTPS implementation in Apache CXF.