What is the severity of CVE-2019-20625?

CVE-2019-20625 is classified as a high severity vulnerability due to its potential for information disclosure.

How does CVE-2019-20625 affect devices?

CVE-2019-20625 affects Samsung mobile devices running Android 7.1 and 8.x on Exynos chipsets, allowing unauthorized information access.

How do I fix CVE-2019-20625?

To fix CVE-2019-20625, users should update their affected Samsung devices to the latest security patch provided by Samsung.

What are the consequences of CVE-2019-20625?

The consequences of CVE-2019-20625 include the potential unauthorized disclosure of sensitive information from the device.

Is my device affected by CVE-2019-20625?

Devices running Android 7.1 or 8.x on Exynos chipsets, particularly those from Samsung, are at risk due to CVE-2019-20625.

Vulnerability/
CVE-2019-20625

low

3.3

CWE

532

24/3/2020

5/8/2024

CVE-2019-20625

First published: Tue Mar 24 2020(Updated: )

An issue was discovered on Samsung mobile devices with N(7.1) and O(8.x) (Exynos chipsets) software. The ion debugfs driver allows information disclosure. The Samsung ID is SVE-2018-13427 (February 2019).

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Google Android	=7.1
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-2019-20625?
CVE-2019-20625 is classified as a high severity vulnerability due to its potential for information disclosure.
How does CVE-2019-20625 affect devices?
CVE-2019-20625 affects Samsung mobile devices running Android 7.1 and 8.x on Exynos chipsets, allowing unauthorized information access.
How do I fix CVE-2019-20625?
To fix CVE-2019-20625, users should update their affected Samsung devices to the latest security patch provided by Samsung.
What are the consequences of CVE-2019-20625?
The consequences of CVE-2019-20625 include the potential unauthorized disclosure of sensitive information from the device.
Is my device affected by CVE-2019-20625?
Devices running Android 7.1 or 8.x on Exynos chipsets, particularly those from Samsung, are at risk due to CVE-2019-20625.

agent/type
agent/softwarecombine
collector/nvd-index
agent/software-canonical-lookup-request
collector/mitre-cve
source/MITRE
agent/weakness
agent/author
agent/references
agent/last-modified-date
agent/severity
agent/tags
agent/description
agent/first-publish-date
agent/event
agent/source
vendor/google
canonical/google android
version/google android/7.1
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-2019-20625?
CVE-2019-20625 is classified as a high severity vulnerability due to its potential for information disclosure.
How does CVE-2019-20625 affect devices?
CVE-2019-20625 affects Samsung mobile devices running Android 7.1 and 8.x on Exynos chipsets, allowing unauthorized information access.
How do I fix CVE-2019-20625?
To fix CVE-2019-20625, users should update their affected Samsung devices to the latest security patch provided by Samsung.
What are the consequences of CVE-2019-20625?
The consequences of CVE-2019-20625 include the potential unauthorized disclosure of sensitive information from the device.
Is my device affected by CVE-2019-20625?
Devices running Android 7.1 or 8.x on Exynos chipsets, particularly those from Samsung, are at risk due to CVE-2019-20625.