Version: v.9 (9)
arm
Package: com.nowsecure.android.vts
1,103 downloads
5.01 MB (5,252,516 bytes)
Min: Android 4.0.3 (Ice Cream Sandwich MR1, API 15)
Target: Android 6.0 (Marshmallow, API 23)
nodpi
Uploaded November 21, 2015 at 12:51AM UTC by Artem Russakovskii
Download APK
There's a newer version available below!

Whoa there!

It looks like you're using an ad blocker, so you'll have to wait 15 more seconds.
Please whitelist this site to skip the wait and help us pay for bandwidth, hosting, and other bills.

APK Notes:

What's new:
Add check for CVE-2015-6608
Added the ability to (optionally, explicitly, and anonymously) share data publicly
Change unreadable text on failed tests
Fix race condition with running stagefright media files


Description:
This tool probes your device for publicly-known system vulnerabilities. All data will stay on your device and will not be shared without your explicit consent. If the app says you're affected, please read www.nowsecure.com/blog/2015/11/18/my-device-is-vulnerable-now-what/. This application is not malicious, and because it’s an open-source project you can see this for yourself on the app’s Github repo github.com/nowsecure/android-vts.
Please file any bugs, issues, or feature requests at: github.com/nowsecure/android-vts/issues. Note that some anti-virus programs may flag this application because it probes the device for weaknesses.

This tool is meant to show the end user the attack surface that a given device is susceptible to. In implementing these checks we attempt to minimize or eliminate both false positives/false negatives without negatively affecting system stability. The application is open source and you can contribute or review the source code at github.com/nowsecure/android-vts.

When a vulnerability is discovered, Google receives word and applies a patch to Android. The Nexus devices are usually the devices that receive these patches quickest as they deviate the least (read: not all) from AOSP (Android Open Source Project - The core of Android, where Google commits to). The lag time between learning about a bug and the time when a patch is applied to a device can still be significant (for OEMs, it can be > 1 year or never). For example, the futex bug (CVE-2014-3153/Towelroot) was known about in late May, early June. This bug took multiple months to get patched on the flagship (at the time) Nexus 5. This leaves users extremely vulnerable to attack from applications. Users mostly do not know that their devices are vulnerable and this tool is meant to give visibility into the vulnerabilities a given device is susceptible to.

Add check for CVE-2015-6608
Added the ability to (optionally, explicitly, and anonymously) share data publicly
Change unreadable text on failed tests
Fix race condition with running stagefright media files
This tool probes your device for publicly-known system vulnerabilities. All data will stay on your device and will not be shared without your explicit consent. If the app says you're affected, please read www.nowsecure.com/blog/2015/11/18/my-device-is-vulnerable-now-what/. This application is not malicious, and because it’s an open-source project you can see this for yourself on the app’s Github repo github.com/nowsecure/android-vts.
Please file any bugs, issues, or feature requests at: github.com/nowsecure/android-vts/issues. Note that some anti-virus programs may flag this application because it probes the device for weaknesses.

This tool is meant to show the end user the attack surface that a given device is susceptible to. In implementing these checks we attempt to minimize or eliminate both false positives/false negatives without negatively affecting system stability. The application is open source and you can contribute or review the source code at github.com/nowsecure/android-vts.

When a vulnerability is discovered, Google receives word and applies a patch to Android. The Nexus devices are usually the devices that receive these patches quickest as they deviate the least (read: not all) from AOSP (Android Open Source Project - The core of Android, where Google commits to). The lag time between learning about a bug and the time when a patch is applied to a device can still be significant (for OEMs, it can be > 1 year or never). For example, the futex bug (CVE-2014-3153/Towelroot) was known about in late May, early June. This bug took multiple months to get patched on the flagship (at the time) Nexus 5. This leaves users extremely vulnerable to attack from applications. Users mostly do not know that their devices are vulnerable and this tool is meant to give visibility into the vulnerabilities a given device is susceptible to.
All versions
December 15, 2015
December 11, 2015
November 21, 2015
Comments