What is the severity of CVE-2020-25056?

CVE-2020-25056 is classified as a high-severity vulnerability due to the risks it poses in improper bootloading.

How do I fix CVE-2020-25056?

To fix CVE-2020-25056, update your Samsung device to the latest software version that addresses this vulnerability.

What devices are affected by CVE-2020-25056?

CVE-2020-25056 affects Samsung mobile devices running Android 10.0, particularly the Galaxy S20.

What is the nature of the vulnerability in CVE-2020-25056?

CVE-2020-25056 arises from improper version checks in the HAL related to the bootloading process by the S.LSI NFC chipset.

When was CVE-2020-25056 disclosed?

CVE-2020-25056 was disclosed in August 2020 as part of the Samsung security updates.

Vulnerability/
CVE-2020-25056

high

7.5

CWE

754

31/8/2020

4/8/2024

CVE-2020-25056

First published: Mon Aug 31 2020(Updated: )

An issue was discovered on Samsung mobile devices with Q(10.0) (Galaxy S20) software. Because HAL improperly checks versions, bootloading by the S.LSI NFC chipset is mishandled. The Samsung ID is SVE-2020-16169 (August 2020).

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Google Android	=10.0
Samsung Galaxy S20

Never miss a vulnerability like this again

Reference Links

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

Frequently Asked Questions

What is the severity of CVE-2020-25056?
CVE-2020-25056 is classified as a high-severity vulnerability due to the risks it poses in improper bootloading.
How do I fix CVE-2020-25056?
To fix CVE-2020-25056, update your Samsung device to the latest software version that addresses this vulnerability.
What devices are affected by CVE-2020-25056?
CVE-2020-25056 affects Samsung mobile devices running Android 10.0, particularly the Galaxy S20.
What is the nature of the vulnerability in CVE-2020-25056?
CVE-2020-25056 arises from improper version checks in the HAL related to the bootloading process by the S.LSI NFC chipset.
When was CVE-2020-25056 disclosed?
CVE-2020-25056 was disclosed in August 2020 as part of the Samsung security updates.

agent/type
agent/softwarecombine
collector/nvd-index
agent/software-canonical-lookup-request
collector/mitre-cve
source/MITRE
agent/references
agent/severity
agent/author
agent/last-modified-date
agent/weakness
agent/tags
agent/description
agent/first-publish-date
agent/event
agent/source
vendor/google
canonical/google android
version/google android/10.0
vendor/samsung
canonical/samsung galaxy s20

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-2020-25056?
CVE-2020-25056 is classified as a high-severity vulnerability due to the risks it poses in improper bootloading.
How do I fix CVE-2020-25056?
To fix CVE-2020-25056, update your Samsung device to the latest software version that addresses this vulnerability.
What devices are affected by CVE-2020-25056?
CVE-2020-25056 affects Samsung mobile devices running Android 10.0, particularly the Galaxy S20.
What is the nature of the vulnerability in CVE-2020-25056?
CVE-2020-25056 arises from improper version checks in the HAL related to the bootloading process by the S.LSI NFC chipset.
When was CVE-2020-25056 disclosed?
CVE-2020-25056 was disclosed in August 2020 as part of the Samsung security updates.