CVE-2024-20053 Memory corruption in MT2713, MT2737, MT6781, MT6789, MT6835, MT6855, MT6879, MT6880, MT6886, MT6890, MT6895, MT6980, MT6983, MT6985, MT6989, MT6990, MT8167, MT8168, MT8173, MT8175, MT8188, MT8195, MT8321, MT8362A, MT8365, MT8385, MT8390, MT8395, MT8666, MT8667, MT8673, MT8765, MT8766, MT8768, MT8781, MT8786, MT8788, MT8789, MT8791, MT8791T, MT8796, MT8797, MT8798

High 8.4 Published Updated

A local attacker with system privileges can exploit an out-of-bounds write in flashc to escalate privileges on MediaTek devices.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Local or same network only
Victim action needed
Not needed
Fix
None listed

What is CVE-2024-20053?

CVE-2024-20053 is a high-severity memory corruption vulnerability in Google Android, published on 1 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

In flashc, there is a possible out of bounds write due to an uncaught exception. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS08541757; Issue ID: ALPS08541764.

Weakness: CWE-787

Which versions are affected by CVE-2024-20053?

It affects 4 products.

Products include Google Android, Linuxfoundation Yocto, Openwrt Openwrt, Rdkcentral Rdk-B.

How do I fix CVE-2024-20053?

No fix has been published for CVE-2024-20053 yet. Limit exposure of the affected software until one is available.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2024-20053 being exploited?

There is no known exploitation of CVE-2024-20053 in the wild and no public exploit code.

All Google Android vulnerabilities

Sources

Also known as GHSA-37h8-7f9x-vvj8.

Is CVE-2024-20053 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free