Android SDK vulnerabilitiesRanked by how likely they are to be used.
Android SDK is made by Google. We track 3 published vulnerabilities listed under that exact name, across 8 versions. None of them is on the list of flaws known to be exploited today. Google lists newer releases under their own names, such as Android SDK Platform Tools, so check those pages too.
We keep watching the known-exploited list.
Is Android SDK listed under other names? Yes.
Google also lists Android SDK under more specific names, such as Android SDK Platform Tools. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which Android SDK vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Android SDK's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Android SDK flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 4.9%CVE-2008-0986High
Integer overflow in the BMP::readFromStream method in the libsgl.so library in Google Android SDK m3-rc37a and earlier, and m5-rc14, allows remote attackers to execute arbitrary code via a crafted BMP file with a...
- 4.6%CVE-2008-0985Medium
Heap-based buffer overflow in the GIF library in the WebKit framework for Google Android SDK m3-rc37a and earlier allows remote attackers to execute arbitrary code via a crafted GIF file whose logical screen height...
- 1.2%CVE-2011-1001Medium
dexdump in Android SDK before 2.3 does not properly perform structural verification, which allows user-assisted remote attackers to cause a denial of service (dexdump crash) and possibly execute arbitrary code via a...
Running Android SDK? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Integer overflow in the BMP::readFromStream method in the libsgl.so library in Google Android SDK m3-rc37a and earlier, and m5-rc14, allows remote attackers to execute arbitrary code via a crafted BMP file with a header containing a negative offset field.
- Matched to
- Android SDK on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 3 published vulnerabilities listed under the name Android SDK, across 8 versions.
None of Android SDK's vulnerabilities is on the list of flaws known to be exploited today.
Google also lists Android SDK under more specific names, such as Android SDK Platform Tools. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a EdgeProtect account and track Android SDK. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.