What is the severity of CVE-2018-21052?

CVE-2018-21052 is considered a high severity vulnerability due to the potential for arbitrary code execution.

How do I fix CVE-2018-21052?

To fix CVE-2018-21052, ensure that your Samsung mobile device has the latest software updates installed.

Which devices are affected by CVE-2018-21052?

CVE-2018-21052 affects Samsung mobile devices with the Android N (7.x) or O (8.x) operating systems on Exynos chipsets.

What type of vulnerability is CVE-2018-21052?

CVE-2018-21052 is a memory safety vulnerability leading to potential arbitrary code execution.

When was CVE-2018-21052 disclosed?

CVE-2018-21052 was disclosed in October 2018.

Vulnerability/
CVE-2018-21052

critical

CWE

119

8/4/2020

5/8/2024

CVE-2018-21052: Buffer Overflow

First published: Wed Apr 08 2020(Updated: )

An issue was discovered on Samsung mobile devices with N(7.x) and O(8.X) (Exynos chipsets) software. There is incorrect usage of shared memory in the vaultkeeper Trustlet, leading to arbitrary code execution. The Samsung ID is SVE-2018-12855 (October 2018).

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Google Android	=7.0
Google Android	=7.1.0
Google Android	=7.1.1
Google Android	=7.1.2
Google Android	=8.0
Google Android	=8.1

Never miss a vulnerability like this again

Reference Links

https://security.samsungmobile.com/securityUpdate.smsb

Frequently Asked Questions

What is the severity of CVE-2018-21052?
CVE-2018-21052 is considered a high severity vulnerability due to the potential for arbitrary code execution.
How do I fix CVE-2018-21052?
To fix CVE-2018-21052, ensure that your Samsung mobile device has the latest software updates installed.
Which devices are affected by CVE-2018-21052?
CVE-2018-21052 affects Samsung mobile devices with the Android N (7.x) or O (8.x) operating systems on Exynos chipsets.
What type of vulnerability is CVE-2018-21052?
CVE-2018-21052 is a memory safety vulnerability leading to potential arbitrary code execution.
When was CVE-2018-21052 disclosed?
CVE-2018-21052 was disclosed in October 2018.

agent/softwarecombine
agent/type
collector/nvd-index
agent/software-canonical-lookup-request
collector/mitre-cve
source/MITRE
agent/severity
agent/weakness
agent/author
agent/last-modified-date
agent/references
agent/tags
agent/description
agent/first-publish-date
agent/event
agent/source
vendor/google
canonical/google android
version/google android/7.0
version/google android/7.1.0
version/google android/7.1.1
version/google android/7.1.2
version/google android/8.0
version/google android/8.1

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2018-21052?
CVE-2018-21052 is considered a high severity vulnerability due to the potential for arbitrary code execution.
How do I fix CVE-2018-21052?
To fix CVE-2018-21052, ensure that your Samsung mobile device has the latest software updates installed.
Which devices are affected by CVE-2018-21052?
CVE-2018-21052 affects Samsung mobile devices with the Android N (7.x) or O (8.x) operating systems on Exynos chipsets.
What type of vulnerability is CVE-2018-21052?
CVE-2018-21052 is a memory safety vulnerability leading to potential arbitrary code execution.
When was CVE-2018-21052 disclosed?
CVE-2018-21052 was disclosed in October 2018.