MediaTek MT8789 Vdec out-of-bounds

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
2.2$0-$5k0.00

Summaryinfo

A vulnerability was found in MediaTek MT6761, MT6765, MT6768, MT6779, MT6785, MT8766, MT8768 and MT8789. It has been rated as problematic. This affects an unknown part of the component Vdec. Performing a manipulation results in out-of-bounds. This vulnerability was named CVE-2024-20117. The attack needs to be approached locally. There is no available exploit. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability classified as problematic has been found in MediaTek MT6761, MT6765, MT6768, MT6779, MT6785, MT8766, MT8768 and MT8789. This affects an unknown function of the component Vdec. The manipulation with an unknown input leads to a out-of-bounds vulnerability. CWE is classifying the issue as CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality. The summary by CVE is:

In vdec, there is a possible out of bounds read due to improper structure design. This could lead to local information disclosure with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS09008925; Issue ID: MSV-1681.

The advisory is shared at corp.mediatek.com. This vulnerability is uniquely identified as CVE-2024-20117 since 11/02/2023. The exploitability is told to be easy. An attack has to be approached locally. Additional levels of successful authentication are necessary for exploitation. Neither technical details nor an exploit are publicly available.

Applying the patch ALPS09008925 is able to eliminate this problem.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 2.3
VulDB Meta Temp Score: 2.2

VulDB Base Score: 2.3
VulDB Temp Score: 2.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Out-of-bounds
CWE: CWE-125 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Patch
Status: 🔍

0-Day Time: 🔍

Patch: ALPS09008925

Timelineinfo

11/02/2023 🔍
11/04/2024 +368 days 🔍
11/04/2024 +0 days 🔍
11/04/2024 +0 days 🔍

Sourcesinfo

Advisory: MSV-1681
Status: Confirmed

CVE: CVE-2024-20117 (🔍)
GCVE (CVE): GCVE-0-2024-20117
GCVE (VulDB): GCVE-100-282933

Entryinfo

Created: 11/04/2024 06:50
Changes: 11/04/2024 06:50 (56)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!