What is the severity of CVE-2014-5871?

CVE-2014-5871 is considered a critical vulnerability due to its potential for man-in-the-middle attacks.

How do I fix CVE-2014-5871?

To fix CVE-2014-5871, users should update the Piwik Mobile 2 application to a version that includes proper SSL certificate validation.

What types of attacks can CVE-2014-5871 facilitate?

CVE-2014-5871 allows man-in-the-middle attackers to spoof SSL servers and obtain sensitive information.

Which version of Piwik Mobile 2 is affected by CVE-2014-5871?

The affected version of Piwik Mobile 2 is 2.0.1 for Android.

What happens if I do not address CVE-2014-5871?

Failing to address CVE-2014-5871 puts users at risk of having their sensitive information intercepted by attackers.

Vulnerability/
CVE-2014-5871

medium

5.4

CWE

310

11/9/2014

6/8/2024

CVE-2014-5871

First published: Thu Sep 11 2014(Updated: )

The Piwik Mobile 2 (aka org.piwik.mobile2) application 2.0.1 for Android does not verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information via a crafted certificate.

Credit: cret@cert.org

Affected Software	Affected Version	How to fix
Piwik Mobile 2	=2.0.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2014-5871?
CVE-2014-5871 is considered a critical vulnerability due to its potential for man-in-the-middle attacks.
How do I fix CVE-2014-5871?
To fix CVE-2014-5871, users should update the Piwik Mobile 2 application to a version that includes proper SSL certificate validation.
What types of attacks can CVE-2014-5871 facilitate?
CVE-2014-5871 allows man-in-the-middle attackers to spoof SSL servers and obtain sensitive information.
Which version of Piwik Mobile 2 is affected by CVE-2014-5871?
The affected version of Piwik Mobile 2 is 2.0.1 for Android.
What happens if I do not address CVE-2014-5871?
Failing to address CVE-2014-5871 puts users at risk of having their sensitive information intercepted by attackers.

agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/references
agent/weakness
agent/author
agent/severity
agent/description
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/piwik
canonical/piwik mobile 2
version/piwik mobile 2/2.0.1

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-2014-5871?
CVE-2014-5871 is considered a critical vulnerability due to its potential for man-in-the-middle attacks.
How do I fix CVE-2014-5871?
To fix CVE-2014-5871, users should update the Piwik Mobile 2 application to a version that includes proper SSL certificate validation.
What types of attacks can CVE-2014-5871 facilitate?
CVE-2014-5871 allows man-in-the-middle attackers to spoof SSL servers and obtain sensitive information.
Which version of Piwik Mobile 2 is affected by CVE-2014-5871?
The affected version of Piwik Mobile 2 is 2.0.1 for Android.
What happens if I do not address CVE-2014-5871?
Failing to address CVE-2014-5871 puts users at risk of having their sensitive information intercepted by attackers.