Mediatek Mt6893 Vulnerabilities

Timeline

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

Last Year

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

Version

NR157
NR167
NR177
12.01
13.01

Grouping all affected versions of a specific product helps to determine existing issues. This makes it possible to determine vendors and products which need attention when it comes to remediations.

Remediation

Official Fix476
Temporary Fix0
Workaround0
Unavailable0
Not Defined0

Vendors and researchers are eager to find countermeasures to mitigate security vulnerabilities. These can be distinguished between multiple forms and levels of remediation which influence risks differently.

Exploitability

High0
Functional0
Proof-of-Concept0
Unproven0
Not Defined476

Researcher and attacker which are looking for security vulnerabilities try to exploit them for academic purposes or personal gain. The level and quality of exploitability can be distinguished to determine simplicity and strength of attacks.

Access Vector

Not Defined0
Physical10
Local414
Adjacent2
Network50

The approach a vulnerability it becomes important to use the expected access vector. This is typically via the network, local, or physically even.

Authentication

Not Defined0
High308
Low143
None25

To exploit a vulnerability a certail level of authentication might be required. Vulnerabilities without such a requirement are much more popular.

User Interaction

Not Defined0
Required9
None467

Some attack scenarios require some user interaction by a victim. This is typical for phishing, social engineering and cross site scripting attacks.

C3BM Index

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

Last Year

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

CVSSv3 Base

≤10
≤20
≤314
≤487
≤5115
≤6170
≤776
≤811
≤91
≤102

The Common Vulnerability Scoring System (CVSS) is an industry standard to define the characteristics and impacts of security vulnerabilities. The base score represents the intrinsic aspects that are constant over time and across user environments. Our unique meta score merges all available scores from different sources to aggregate to the most reliable result.

CVSSv3 Temp

≤10
≤20
≤314
≤4152
≤550
≤6174
≤772
≤811
≤91
≤102

The Common Vulnerability Scoring System (CVSS) uses temp scores to reflect the characteristics of a vulnerability that may change over time but not across user environments. This includes reporting confidence, exploitability and remediation levels. We do also provide our unique meta score for temp scores, even though other sources rarely publish them.

VulDB

≤10
≤20
≤382
≤447
≤5219
≤658
≤758
≤85
≤97
≤100

The moderation team is always defining the base vector and base score for an entry. These and all other available scores are used to generate the meta score.

NVD

≤10
≤20
≤30
≤41
≤568
≤623
≤7177
≤830
≤90
≤103

The National Vulnerability Database (NVD) is also defining CVSS vectors and scores. These are usually not complete and might differ from VulDB scores.

CNA

≤10
≤20
≤30
≤41
≤511
≤62
≤731
≤84
≤92
≤101

A CVE Numbering Authority (CNA) is responsible for assigning new CVE entries. They might also include a CVSS score. These are usually not complete and might differ from VulDB scores.

Vendor

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

Some vendors are willing to publish their own CVSS vectors and scores for vulnerabilities in their products. The coverage varies from vendor to vendor.

Research

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

There are sometimes also security researcher which provide their own CVSS vectors and scores for vulnerabilities they have found and published.

Exploit 0-day

<1k252
<2k167
<5k52
<10k5
<25k0
<50k0
<100k0
≥100k0

The moderation team is working with the threat intelligence team to determine prices for exploits. Our unique algorithm is used to identify the 0-day prices for an exploit, before it got distributed or became public. Calculated prices are aligned to prices disclosed by vulnerability broker and compared to prices we see on exploit markets.

Exploit Today

<1k476
<2k0
<5k0
<10k0
<25k0
<50k0
<100k0
≥100k0

The 0-day prices do not consider time-relevant factors. The today price does reflect price impacts like disclosure of vulnerability details, alternative exploits, availability of countermeasures. These dynamic aspects might decrease the exploit prices over time. Under certain circumstances this happens very fast.

Exploit Market Volume

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

Last Year

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

🔴 CTI Activities

Our unique Cyber Threat Intelligence aims to determine the ongoing research of actors to anticipiate their acitivities. Observing exploit markets on the Darknet, discussions of vulnerabilities on mailinglists, and exchanges on social media makes it possible to identify planned attacks. Monitored actors and activities are classified whether they are offensive or defensive. They are also weighted as some actors are well-known for certain products and technologies. And some of their disclosures might contain more or less details about technical aspects and personal context. The world map highlights active actors in real-time.

Affected Versions (6): 12.0, 13.0, Android 11.0, NR15, NR16, NR17

Software Type: Chip Software

PublishedBaseTempVulnerability0dayTodayExpRemCTICVE
12/02/20245.45.3MediaTek MT9687 Soundtrigger out-of-bounds write$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2024-20135
12/02/20245.45.3MediaTek MT8796 Power stack-based overflow$0-$5k$0-$5kNot DefinedOfficial Fix0.08CVE-2024-20130
12/02/20245.45.3MediaTek MT8798 Vdec out-of-bounds write$0-$5k$0-$5kNot DefinedOfficial Fix0.05CVE-2024-20125
12/02/20245.35.1MediaTek MT6580 Telephony out-of-bounds$0-$5k$0-$5kNot DefinedOfficial Fix0.05CVE-2024-20129
12/02/20246.46.3MediaTek MT6580 Telephony out-of-bounds$0-$5k$0-$5kNot DefinedOfficial Fix0.08CVE-2024-20128
12/02/20246.46.3MediaTek MT6580 Telephony out-of-bounds$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2024-20127
11/04/20244.24.0MediaTek MT8798 KeyInstall out-of-bounds write$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2024-20121
11/04/20244.24.0MediaTek MT8798 out-of-bounds write$0-$5k$0-$5kNot DefinedOfficial Fix0.06CVE-2024-20120
11/04/20244.24.0MediaTek MT8676 Mms write-what-where condition$0-$5k$0-$5kNot DefinedOfficial Fix0.06CVE-2024-20119
11/04/20244.24.0MediaTek MT8792 Mms write-what-where condition$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2024-20118
11/04/20244.24.0MediaTek MT8195 Ccu out-of-bounds write$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2024-20115
11/04/20244.24.0MediaTek MT8195 Ccu out-of-bounds write$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2024-20114
11/04/20244.24.0MediaTek MT8195 Ccu out-of-bounds write$0-$5k$0-$5kNot DefinedOfficial Fix0.06CVE-2024-20111
11/04/20245.45.3MediaTek MT8195 Ccu out-of-bounds write$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2024-20110
11/04/20245.45.3MediaTek MT8195 Ccu out-of-bounds write$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2024-20109
11/04/20245.45.3MediaTek MT8798 Atci out-of-bounds write$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2024-20108
10/07/20244.24.0MediaTek MT8788 Power out-of-bounds write$0-$5k$0-$5kNot DefinedOfficial Fix0.00CVE-2024-20098
10/07/20244.24.0MediaTek MT6768/MT6833/MT6853/MT6877/MT6893/MT8532 Power out-of-bounds write$0-$5k$0-$5kNot DefinedOfficial Fix0.04CVE-2024-20099
10/07/20243.73.7MediaTek MT8678 m4u out-of-bounds$0-$5k$0-$5kNot DefinedOfficial Fix0.05CVE-2024-20096
10/07/20243.73.7MediaTek MT8678 m4u out-of-bounds$0-$5k$0-$5kNot DefinedOfficial Fix0.05CVE-2024-20095
10/07/20246.56.2MediaTek MT8797 Modem NR15 assertion$0-$5k$0-$5kNot DefinedOfficial Fix0.05CVE-2024-20094
09/02/20243.33.3MediaTek MT8796 Keyinstall out-of-bounds$0-$5k$0-$5kNot DefinedOfficial Fix0.03CVE-2024-20088
09/02/20243.73.7MediaTek MT8678 Power out-of-bounds$0-$5k$0-$5kNot DefinedOfficial Fix0.09CVE-2024-20085
09/02/20243.73.7MediaTek MT8678 Power out-of-bounds$0-$5k$0-$5kNot DefinedOfficial Fix0.05CVE-2024-20084
08/14/20249.39.1MediaTek MT6990 Modem memory corruption$5k-$25k$0-$5kNot DefinedOfficial Fix0.04CVE-2024-20082

451 more entries are not shown

more entries by Mediatek

Might our Artificial Intelligence support you?

Check our Alexa App!