Every CVE Search/ Get API key

CVE-2021-0639

In multiple functions of libl3oemcrypto.cpp, there is a possible weakness in the existing...

5.5 MediumFix available

In multiple functions of libl3oemcrypto.cpp, there is a possible weakness in the existing obfuscation mechanism due to the way sensitive data is handled. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android SoCAndroid ID: A-190724551

Attack profile

How easy it is to exploit

Attack vector
Local
Complexity
Low
Privileges needed
Low
User interaction
None

What an attacker can affect

Confidentiality
High
Integrity
None
Availability
None

Exploit likelihood

0.12%Down 0.3 points since Aug 18, 2021
90%50%10%1%

What each source reports

NVD Score used 5.5

In multiple functions of libl3oemcrypto.cpp, there is a possible weakness in the existing obfuscation mechanism due to the way sensitive data is handled. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android SoCAndroid ID: A-190724551

Record
CVE-2021-0639
CVSS 3.1
5.5 MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CVSS 2.0
2.1 LowAV:L/AC:L/Au:N/C:P/I:N/A:N
Weakness
CWE-922
Updated
2026-11-02
CVE List No score

In multiple functions of libl3oemcrypto.cpp, there is a possible weakness in the existing obfuscation mechanism due to the way sensitive data is handled. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android SoCAndroid ID: A-190724551

Record
CVE-2021-0639
Updated
2026-11-02
EUVDEUVD-2021-3258 No score

In multiple functions of libl3oemcrypto.cpp, there is a possible weakness in the existing obfuscation mechanism due to the way sensitive data is handled. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android SoCAndroid ID: A-190724551

Record
EUVD-2021-3258
Updated
2026-11-03
GitHub AdvisoriesGHSA-45mp-7qc4-gj8v No score

In multiple functions of libl3oemcrypto.cpp, there is a possible weakness in the existing...

In multiple functions of libl3oemcrypto.cpp, there is a possible weakness in the existing obfuscation mechanism due to the way sensitive data is handled. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android SoCAndroid ID: A-190724551

Record
GHSA-45mp-7qc4-gj8v
Weakness
CWE-922
Updated
2026-11-02
OSVASB-A-190724551 No score

In multiple functions of libl3oemcrypto.cpp, there is a possible weakness in the existing obfuscation mechanism due to the way sensitive data is handled. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

Record
ASB-A-190724551
Updated
2026-11-10

Affected products

Affected packages

Affected packages
PackageAffectedFixed
:unknown:
Android
SoCVersion:0 up to SoCVersion:2021-08-05, plus listed versions
SoCVersion
SoCVersion:2021-08-05

History

History
RecordedChangedSources
factsOSV
aliasesEUVD
first indexedCVE List, GitHub Advisories, NVD, OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

CVE-2021-0639 is a medium vulnerability (CVSS 5.5) in Google Android, published August 1, 2021. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.12%, the 1st percentile. Fixed in :unknown: SoCVersion:2021-08-05.

References

MoveEnter Open