Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2017-0709

3.3 · LOW

A information disclosure vulnerability in the HTC sensor hub driver.

Published Jul 6, 2017CWE-200EPSS 0.33%

Overview

CVE-2017-0709 is a low-severity vulnerability. It was published on July 6, 2017 and has a CVSS 3.0 base score of 3.3 (LOW).

This vulnerability has a CVSS 3.0 base score of 3.3, rated LOW. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical description

A information disclosure vulnerability in the HTC sensor hub driver. Product: Android. Versions: Android kernel. Android ID: A-35468048.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refwww.securityfocus.com/bid/99474Refsource.android.com/security/bulletin/2017-07-01Refwww.securityfocus.com/bid/99474Refsource.android.com/security/bulletin/2017-07-01

How CyberStrike helps

Frequently asked questions

What is CVE-2017-0709?

CVE-2017-0709 is a low-severity vulnerability. It was published on July 6, 2017 and has a CVSS 3.0 base score of 3.3 (LOW).

How severe is CVE-2017-0709?

This vulnerability has a CVSS 3.0 base score of 3.3, rated LOW. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2017-0709?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2017-0709?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2017-0709 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related LOW CVEs from 2017

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999