CVE-2020-0062
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn Euicc, there is a possible information disclosure due to an included test Certificate. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-143232031
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Euicc (eSIM) component in Android contains a test certificate that was inadvertently included in production builds. This test certificate could be leveraged by remote attackers to authenticate or decrypt eSIM-related communications, leading to unauthorized information disclosure. No user interaction or elevated privileges are required for exploitation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if your device uses eSIM (Euicc) functionalityCheck Android Settings > Network & Internet > SIMs (or similar path depending on Android version) to see if an eSIM profile is provisioned or availableAffected if Device supports and has eSIM capability enabled - the test certificate exposure applies to any Android device with Euicc (eSIM) component
-
Determine if you are using a stock manufacturer/carrier Android buildCheck Settings > About Phone > Build Number. Stock builds from OEMs/carriers include the vulnerable test certificate in the Euicc system componentAffected if Running a stock OEM or carrier Android build - the test certificate was inadvertently included in production images by manufacturers
-
Verify if you have access to inspect system images or custom ROMsIf using custom ROMs or building Android from source, examine the system/connectivity/euicc or related partition/files for embedded certificatesAffected if You build or modify custom ROMs - you can inspect the Euicc component binary/assets for test certificates that should not be present in production
-
Check Android security patch levelGo to Settings > Security > Security Patch Level (or About Phone > Android Security Patch Level)Affected if Security patch level is older than the fix date for CVE-2020-0062 - though note all Android versions were initially affected
You are affected if your Android device supports eSIM (Euicc) and you are running a stock manufacturer build, as the test certificate was embedded in production Euicc components across all Android versions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRemove the test certificate from production Euicc builds and ensure proper certificate management controls prevent debug/test artifacts from shipping in release versions. Apply Android security patches for the affected kernel versions.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-0062 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-0062 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data