What is the severity of CVE-2019-20595?

CVE-2019-20595 has been classified as a high-severity vulnerability due to the potential unauthorized access to Bluetooth functionalities.

How do I fix CVE-2019-20595?

To mitigate CVE-2019-20595, users should update their affected Samsung mobile devices to the latest software version provided by Samsung.

What devices are affected by CVE-2019-20595?

CVE-2019-20595 specifically affects Samsung mobile devices running Android version 9.0 (Pie).

What type of vulnerability is CVE-2019-20595?

CVE-2019-20595 is an authentication-related vulnerability that allows enabling or disabling the Bluetooth stack without proper authentication.

Was CVE-2019-20595 publicly disclosed?

Yes, CVE-2019-20595 was publicly disclosed in July 2019 as part of Samsung's security updates.

Vulnerability/
CVE-2019-20595

low

2.4

CWE

306

24/3/2020

5/8/2024

CVE-2019-20595

First published: Tue Mar 24 2020(Updated: )

An issue was discovered on Samsung mobile devices with P(9.0) software. Quick Panel allows enabling or disabling the Bluetooth stack without authentication. The Samsung ID is SVE-2019-14545 (July 2019).

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Google Android	=9.0

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-20595?
CVE-2019-20595 has been classified as a high-severity vulnerability due to the potential unauthorized access to Bluetooth functionalities.
How do I fix CVE-2019-20595?
To mitigate CVE-2019-20595, users should update their affected Samsung mobile devices to the latest software version provided by Samsung.
What devices are affected by CVE-2019-20595?
CVE-2019-20595 specifically affects Samsung mobile devices running Android version 9.0 (Pie).
What type of vulnerability is CVE-2019-20595?
CVE-2019-20595 is an authentication-related vulnerability that allows enabling or disabling the Bluetooth stack without proper authentication.
Was CVE-2019-20595 publicly disclosed?
Yes, CVE-2019-20595 was publicly disclosed in July 2019 as part of Samsung's security updates.

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

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-20595?
CVE-2019-20595 has been classified as a high-severity vulnerability due to the potential unauthorized access to Bluetooth functionalities.
How do I fix CVE-2019-20595?
To mitigate CVE-2019-20595, users should update their affected Samsung mobile devices to the latest software version provided by Samsung.
What devices are affected by CVE-2019-20595?
CVE-2019-20595 specifically affects Samsung mobile devices running Android version 9.0 (Pie).
What type of vulnerability is CVE-2019-20595?
CVE-2019-20595 is an authentication-related vulnerability that allows enabling or disabling the Bluetooth stack without proper authentication.
Was CVE-2019-20595 publicly disclosed?
Yes, CVE-2019-20595 was publicly disclosed in July 2019 as part of Samsung's security updates.