medium
4.3
CWE
310 319
Advisory Published
CVE Published
Advisory Published
Updated

CVE-2014-0035

First published: Fri May 02 2014(Updated: )

The SymmetricBinding in Apache CXF before 2.6.13 and 2.7.x before 2.7.10, when EncryptBeforeSigning is enabled and the UsernameToken policy is set to an EncryptedSupportingToken, transmits the UsernameToken in cleartext, which allows remote attackers to obtain sensitive information by sniffing the network.

Credit: secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
maven/org.apache.cxf:cxf-core>=2.7.0<2.7.10
2.7.10
maven/org.apache.cxf:cxf-core<2.6.13
2.6.13
redhat/cxf<2.6.14
2.6.14
redhat/cxf<2.7.11
2.7.11
Apache CXF<=2.6.12
Apache CXF=2.6.0
Apache CXF=2.6.1
Apache CXF=2.6.2
Apache CXF=2.6.3
Apache CXF=2.6.4
Apache CXF=2.6.5
Apache CXF=2.6.6
Apache CXF=2.6.7
Apache CXF=2.6.8
Apache CXF=2.6.9
Apache CXF=2.6.10
Apache CXF=2.6.11
Apache CXF=2.7.0
Apache CXF=2.7.1
Apache CXF=2.7.2
Apache CXF=2.7.3
Apache CXF=2.7.4
Apache CXF=2.7.5
Apache CXF=2.7.6
Apache CXF=2.7.7
Apache CXF=2.7.8
Apache CXF=2.7.9
JBoss Enterprise Application Platform=6.0.0
JBoss Enterprise Application Platform=6.2.0

Remedy

http://svn.apache.org/viewvc?view=revision&revision=1564724

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2014-0035?

    CVE-2014-0035 has a medium severity as it allows sensitive information to be transmitted in cleartext.

  • How do I fix CVE-2014-0035?

    To fix CVE-2014-0035, you should upgrade to Apache CXF version 2.6.13 or 2.7.10, or later.

  • What versions of Apache CXF are affected by CVE-2014-0035?

    CVE-2014-0035 affects Apache CXF versions prior to 2.6.13 and 2.7.x versions before 2.7.10.

  • What is the impact of CVE-2014-0035?

    The impact of CVE-2014-0035 is that it may expose username tokens to attackers, leading to unauthorized access.

  • Is there a workaround for CVE-2014-0035 if I cannot upgrade?

    There is no specific workaround for CVE-2014-0035; upgrading to a patched version is recommended.

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203