Tizen vulnerabilitiesRanked by how likely they are to be used.
Tizen is made by Linux. We track 13 published vulnerabilities in it, across 11 versions. None of them is on the list of flaws known to be exploited today. If you run Tizen, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Tizen vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Tizen's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Tizen 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.
- 2.4%CVE-2021-25437Critical
Improper access control vulnerability in Tizen FOTA service prior to Firmware update JUL-2021 Release allows attackers to arbitrary code execution by replacing FOTA update file.
- 1.7%CVE-2021-25434Critical
Improper input validation vulnerability in Tizen bootloader prior to Firmware update JUL-2021 Release allows arbitrary code execution using param partition in wireless firmware download mode.
- 1.7%CVE-2021-25435Critical
Improper input validation vulnerability in Tizen bootloader prior to Firmware update JUL-2021 Release allows arbitrary code execution using recovery partition in wireless firmware download mode.
- 1.6%CVE-2021-25436Critical
Improper input validation vulnerability in Tizen FOTA service prior to Firmware update JUL-2021 Release allows arbitrary code execution via Samsung Accessory Protocol.
- 1.1%CVE-2012-6459Medium
ConnMan 1.3 on Tizen continues to list the bluetooth service after offline mode has been enabled, which might allow remote attackers to obtain sensitive information via Bluetooth packets.
- 0.8%CVE-2018-16263High
The PulseAudio system service in Tizen allows an unprivileged process to control its A2DP MediaEndpoint, due to improper D-Bus security policy configurations.
- 0.8%CVE-2018-16262High
The pkgmgr system service in Tizen allows an unprivileged process to perform package management actions, due to improper D-Bus security policy configurations.
- 0.7%CVE-2018-16266High
The Enlightenment system service in Tizen allows an unprivileged process to fully control or capture windows, due to improper D-Bus security policy configurations.
- 0.7%CVE-2018-16267High
The system-popup system service in Tizen allows an unprivileged process to perform popup-related system actions, due to improper D-Bus security policy configurations.
- 0.6%CVE-2018-16265Medium
The bt/bt_core system service in Tizen allows an unprivileged process to create a system user interface and control the Bluetooth pairing process, due to improper D-Bus security policy configurations.
Running Tizen? 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
Improper access control vulnerability in Tizen FOTA service prior to Firmware update JUL-2021 Release allows attackers to arbitrary code execution by replacing FOTA update file.
- Matched to
- Tizen 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 13 published vulnerabilities listed under the name Tizen, across 11 versions.
None of Tizen's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Tizen. 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.