Samsung Mobile vulnerabilitiesRanked by how likely they are to be used.
Samsung Mobile is made by Samsung. We track 28 published vulnerabilities in it, across 12 versions. None of them is on the list of flaws known to be exploited today. If you run Samsung Mobile, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Samsung Mobile vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Samsung Mobile's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Samsung Mobile 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.
- 8.7%CVE-2018-10751Medium
A malformed OMACP WAP push message can cause memory corruption on a Samsung S7 Edge device when processing the String Extension portion of the WbXml payload.
- 7.0%CVE-2015-7896Medium
LibQJpeg in the Samsung Galaxy S6 before the October 2015 MR allows remote attackers to cause a denial of service (memory corruption and SIGSEGV) via a crafted image file.
- 2.9%CVE-2017-5538Critical
The kbase_dispatch function in arm/t7xx/r5p0/mali_kbase_core_linux.c in the GPU driver on Samsung devices with M(6.0) and N(7.0) software and Exynos AP chipsets allows attackers to have unspecified impact via unknown...
- 2.5%CVE-2018-9139Critical
On Samsung mobile devices with N(7.x) software, a buffer overflow in the vision service allows code execution in a privileged process via a large frame size, aka SVE-2017-11165.
- 2.4%CVE-2018-9141High
On Samsung mobile devices with L(5.x), M(6.0), and N(7.x) software, Gallery allows remote attackers to execute arbitrary code via a BMP file with a crafted resolution, aka SVE-2017-11105.
- 2.3%CVE-2018-9143Critical
On Samsung mobile devices with M(6.0) and N(7.x) software, a heap overflow in the sensorhub binder service leads to code execution in a privileged process, aka SVE-2017-10991.
- 1.8%CVE-2018-5210High
On Samsung mobile devices with N(7.x) software and Exynos chipsets, attackers can conduct a Trustlet stack overflow attack for arbitrary TEE code execution, in conjunction with a brute-force attack to discover unlock...
Running Samsung Mobile? 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
A malformed OMACP WAP push message can cause memory corruption on a Samsung S7 Edge device when processing the String Extension portion of the WbXml payload. This is due to an integer overflow in memory allocation for this string. The Samsung ID is SVE-2018-11463.
- Matched to
- Samsung Mobile 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 28 published vulnerabilities listed under the name Samsung Mobile, across 12 versions.
None of Samsung Mobile's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Samsung Mobile. 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.