CVE-2020-27049 Memory corruption in Android

High 7.8 Published Updated

A missing bounds check in Android's NFC stack allows local attackers to escalate privileges via an out-of-bounds write.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Local or same network only
Victim action needed
A user has to click or open something
Fix
None listed

What is CVE-2020-27049?

CVE-2020-27049 is a high-severity memory corruption vulnerability in Google Android, published on 15 Dec 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

Official description

In rw_t3t_send_raw_frame of rw_t3t.cc, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-11Android ID: A-157649467

Weakness: CWE-787

Which versions are affected by CVE-2020-27049?

It affects 1 product.

Products include Google Android.

How do I fix CVE-2020-27049?

No fix has been published for CVE-2020-27049 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-2020-27049 being exploited?

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

All Google Android vulnerabilities

Sources

Also known as GHSA-555x-c8f3-84gj.

Is CVE-2020-27049 in your software?

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

Check your SBOMs for free