Mt8163 vulnerabilitiesRanked by how likely they are to be used.
Mt8163 is made by Mediatek. We track 46 published vulnerabilities listed under that exact name, across 0 versions. None of them is on the list of flaws known to be exploited today. Mediatek lists newer releases under their own names, such as Mt8163 Firmware, so check those pages too.
We keep watching the known-exploited list.
Is Mt8163 listed under other names? Yes.
Mediatek also lists Mt8163 under more specific names, such as Mt8163 Firmware. 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 Mt8163 vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Mt8163's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Mt8163 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.
- 3.2%CVE-2019-15027Critical
The MediaTek Embedded Multimedia Card (eMMC) subsystem for Android on MT65xx, MT66xx, and MT8163 SoC devices allows attackers to execute arbitrary commands as root via shell metacharacters in a filename under /data,...
- 0.7%CVE-2022-26447Critical
In BT firmware, there is a possible out of bounds write due to a missing bounds check.
- 0.5%CVE-2021-0675High
In alac decoder, there is a possible out of bounds write due to an incorrect bounds check.
- 0.5%CVE-2021-0674Medium
In alac decoder, there is a possible out of bounds read due to an incorrect bounds check.
- 0.4%CVE-2024-20009High
In alac decoder, there is a possible out of bounds write due to an incorrect error handling.
- 0.3%CVE-2024-20028Medium
In da, there is a possible out of bounds write due to lack of valudation.
- 0.3%CVE-2022-20022Medium
In Bluetooth, there is a possible link disconnection due to bluetooth does not properly handle a connection attempt from a host with the same BD address as the currently connected BT host.
- 0.3%CVE-2022-20023Medium
In Bluetooth, there is a possible application crash due to bluetooth flooding a device with LMP_AU_rand packet.
- 0.3%CVE-2022-20021Medium
In Bluetooth, there is a possible application crash due to bluetooth does not properly handle the reception of multiple LMP_host_connection_req.
- 0.2%CVE-2022-20073Medium
In preloader (usb), there is a possible out of bounds write due to a integer underflow.
Running Mt8163? 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
The MediaTek Embedded Multimedia Card (eMMC) subsystem for Android on MT65xx, MT66xx, and MT8163 SoC devices allows attackers to execute arbitrary commands as root via shell metacharacters in a filename under /data, because clear_emmc_nomedia_entry in platform/mt6577/external/meta/emmc/meta_clr_emmc.c invokes 'system("/system/bin/rm -r /data/' followed by this filename upon an eMMC clearance from a Meta Mode boot. NOTE: compromise of Fire OS on the Amazon Echo Dot would require a second hypothetical vulnerability that allows creation of the required file under /data.
- Matched to
- Mt8163 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 46 published vulnerabilities listed under the name Mt8163, across 0 versions.
None of Mt8163's vulnerabilities is on the list of flaws known to be exploited today.
Mediatek also lists Mt8163 under more specific names, such as Mt8163 Firmware. 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 Mt8163. 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.