PatchTheCVEruntastic vulnerabilities
Recent CVEs affecting runtastic products. 7 tracked.
runtastic has 7 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2014-09-09. Highest priority: CVE-2014-5690 (score 25/100).
- CVE-2014-5690 MEDIUM 5.4 DOWNGRADE The Runtastic Timer (aka com.runtastic.android.timer) application 1.0.1 for Android does not verify X.509 cert
- CVE-2014-5689 MEDIUM 5.4 DOWNGRADE The Runtastic Road Bike (aka com.runtastic.android.roadbike.lite) application 2.0.1 for Android does not verif
- CVE-2014-5688 MEDIUM 5.4 DOWNGRADE The Runtastic Pedometer (aka com.runtastic.android.pedometer.lite) application 1.5 for Android does not verify
- CVE-2014-5687 MEDIUM 5.4 DOWNGRADE The Runtastic Mountain Bike (aka com.runtastic.android.mountainbike.lite) application 2.0.1 for Android does n
- CVE-2014-5686 MEDIUM 5.4 DOWNGRADE The Runtastic Me (aka com.runtastic.android.me.lite) application 1.0.2 for Android does not verify X.509 certi
- CVE-2014-5685 MEDIUM 5.4 DOWNGRADE The Runtastic Heart Rate (aka com.runtastic.android.heartrate.lite) application 1.3 for Android does not verif
- CVE-2014-5684 MEDIUM 5.4 DOWNGRADE The Runtastic Running & Fitness (aka com.runtastic.android) application 5.1.2 for Android does not verify X.50
FAQ
How do I fix runtastic vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is runtastic being exploited right now?
None of the tracked runtastic CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which runtastic CVE should I patch first?
CVE-2014-5690 currently ranks highest (25/100): The Runtastic Timer (aka com.runtastic.android.timer) application 1.0.1 for Android does not verify X.509 cert.