What is the severity of CVE-2017-17945?

CVE-2017-17945 is considered a high severity vulnerability due to its lack of SSL certificate validation.

How do I fix CVE-2017-17945?

To fix CVE-2017-17945, update the ASUS HiVivo application to version 5.6.27 or later.

What systems are affected by CVE-2017-17945?

CVE-2017-17945 affects the ASUS HiVivo application before version 5.6.27 and ASUS Vivobaby application before version 1.1.09.

What are the implications of CVE-2017-17945?

The implications of CVE-2017-17945 include the potential for man-in-the-middle attacks due to missing SSL certificate validation.

Who is affected by CVE-2017-17945?

Users of ASUS Watch devices using the HiVivo application and parents using the Vivobaby application are affected by CVE-2017-17945.

Vulnerability/
CVE-2017-17945

critical

9.1

CWE

295

24/6/2019

5/8/2024

CVE-2017-17945

First published: Mon Jun 24 2019(Updated: )

The ASUS HiVivo aspplication before 5.6.27 for ASUS Watch has Missing SSL Certificate Validation.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Asus Hivivo	<5.6.27
Asus Vivobaby	<1.1.09

Never miss a vulnerability like this again

Reference Links

http://firstsight.me/2017/12/lack-of-binary-protection-at-asus-vivo-baby-and-hivivo-for-android-that-could-result-of-several-security-issues

Frequently Asked Questions

What is the severity of CVE-2017-17945?
CVE-2017-17945 is considered a high severity vulnerability due to its lack of SSL certificate validation.
How do I fix CVE-2017-17945?
To fix CVE-2017-17945, update the ASUS HiVivo application to version 5.6.27 or later.
What systems are affected by CVE-2017-17945?
CVE-2017-17945 affects the ASUS HiVivo application before version 5.6.27 and ASUS Vivobaby application before version 1.1.09.
What are the implications of CVE-2017-17945?
The implications of CVE-2017-17945 include the potential for man-in-the-middle attacks due to missing SSL certificate validation.
Who is affected by CVE-2017-17945?
Users of ASUS Watch devices using the HiVivo application and parents using the Vivobaby application are affected by CVE-2017-17945.

collector/nvd-index
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/author
agent/severity
agent/weakness
agent/last-modified-date
agent/references
agent/description
agent/first-publish-date
agent/event
agent/tags
agent/source
vendor/asus
canonical/asus hivivo
canonical/asus vivobaby

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-2017-17945?
CVE-2017-17945 is considered a high severity vulnerability due to its lack of SSL certificate validation.
How do I fix CVE-2017-17945?
To fix CVE-2017-17945, update the ASUS HiVivo application to version 5.6.27 or later.
What systems are affected by CVE-2017-17945?
CVE-2017-17945 affects the ASUS HiVivo application before version 5.6.27 and ASUS Vivobaby application before version 1.1.09.
What are the implications of CVE-2017-17945?
The implications of CVE-2017-17945 include the potential for man-in-the-middle attacks due to missing SSL certificate validation.
Who is affected by CVE-2017-17945?
Users of ASUS Watch devices using the HiVivo application and parents using the Vivobaby application are affected by CVE-2017-17945.