Galaxy S4 Mini vulnerabilitiesRanked by how likely they are to be used.

Product0 versions
The short answer

Galaxy S4 Mini is made by Samsung. We track 9 published vulnerabilities listed under that exact name, across 0 versions. None of them is on the list of flaws known to be exploited today. Samsung lists newer releases under their own names, such as Galaxy S4 Mini Firmware, so check those pages too.

See the riskiest flaws

We keep watching the known-exploited list.

Other names

Is Galaxy S4 Mini listed under other names? Yes.

Samsung also lists Galaxy S4 Mini under more specific names, such as Galaxy S4 Mini Firmware and Galaxy S4 Mini Lte. 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.

Known exploited

Which Galaxy S4 Mini vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Galaxy S4 Mini's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Galaxy S4 Mini 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.

50% or more10% to 49%Under 10%
  1. 2.1%

    On Samsung Galaxy S4 through S7 devices, an integer overflow condition exists within libomacp.so when parsing OMACP messages (within WAP Push SMS messages) leading to a heap corruption that can result in Denial of...

    CVSS9.8Published31 Oct 2016
  2. 0.6%

    On Samsung Galaxy S4 through S7 devices, absence of permissions on the BroadcastReceiver responsible for handling the com.[Samsung].android.intent.action.SET_WIFI intent leads to unsolicited configuration messages...

    CVSS7.5Published31 Oct 2016
  3. 0.6%

    On Samsung Galaxy S4 through S7 devices, a malformed OTA WAP PUSH SMS containing an OMACP message sent remotely triggers an unhandled ArrayIndexOutOfBoundsException in Samsung's implementation of the WifiServiceImpl...

    CVSS7.5Published31 Oct 2016
  4. 0.5%

    Samsung SM-G920F build G920FXXU2COH2 (Galaxy S6), SM-N9005 build N9005XXUGBOK6 (Galaxy Note 3), GT-I9192 build I9192XXUBNB1 (Galaxy S4 mini), GT-I9195 build I9195XXUCOL1 (Galaxy S4 mini LTE), and GT-I9505 build...

    CVSS6.8Published13 Apr 2017
  5. 0.5%

    On Samsung Galaxy S4 through S7 devices, the "omacp" app ignores security information embedded in the OMACP messages resulting in remote unsolicited WAP Push SMS messages being accepted, parsed, and handled by the...

    CVSS7.5Published31 Oct 2016
Precursor Intelligence

Running Galaxy S4 Mini? 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.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. 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.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 9 published vulnerabilities listed under the name Galaxy S4 Mini, across 0 versions.

None of Galaxy S4 Mini's vulnerabilities is on the list of flaws known to be exploited today.

Samsung also lists Galaxy S4 Mini under more specific names, such as Galaxy S4 Mini Firmware and Galaxy S4 Mini Lte. 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 Precursor Intelligence account and track Galaxy S4 Mini. 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.