CVE-2018-21063 An issue was discovered on Samsung mobile devices with M(6.0), N(7.x), and O(8.x) (Exynos chipsets) software.
Critical 9.8
Published
Updated
Check this codebase for CVE-2018-21063 and fix it if it is affected.
What it is: CVE-2018-21063 is a critical vulnerability in Google Android, published on 8 Apr 2020.
Exploitation: There is no known exploitation of CVE-2018-21063 in the wild and no public exploit code.
Affected product: Google Android. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2018-21063/ (Markdown: https://insights.sbomify.com/CVE-2018-21063/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2018-21063?
CVE-2018-21063 is a critical vulnerability in Google Android, published on 8 Apr 2020.
Official description
An issue was discovered on Samsung mobile devices with M(6.0), N(7.x), and O(8.x) (Exynos chipsets) software. Keymaster has an architectural problem because tlApi in TEE is not properly protected. The Samsung ID is SVE-2018-11792 (August 2018).
Which versions are affected by CVE-2018-21063?
It affects 1 product.
Products include Google Android.
How do I fix CVE-2018-21063?
No fix has been published for CVE-2018-21063 yet. Limit exposure of the affected software until one is available.
Is CVE-2018-21063 being exploited?
There is no known exploitation of CVE-2018-21063 in the wild and no public exploit code.
Other vulnerabilities in Google Android
Sources
Also known as GHSA-mmfj-vg4h-326c.