# CVE-2017-8360: Information disclosure in n/a

> Local attackers can read sensitive keystroke data logged by the Conexant mictray64 utility via debug messages or public log files.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-cfm5-hvqf-hqgc

## What is CVE-2017-8360?

CVE-2017-8360 is a medium-severity vulnerability in n/a, published on 12 May 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Conexant Systems mictray64 task, as used on HP Elite, EliteBook, ProBook, and ZBook systems, leaks sensitive data (keystrokes) to any process. In mictray64.exe (mic tray icon) 1.0.0.46, a LowLevelKeyboardProc Windows hook is used to capture keystrokes. This data is leaked via unintended channels: debug messages accessible to any process that is running in the current user session, and filesystem access to C:\Users\Public\MicTray.log by any process.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2017-8360?

It affects 1 product.


Products: Conexant Mictray64.

## How do I fix CVE-2017-8360?

No fix has been published for CVE-2017-8360 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-8360 being exploited?

There is no known exploitation of CVE-2017-8360 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-8360 and fix it if it is affected.

What it is: CVE-2017-8360 is a medium-severity vulnerability in n/a, published on 12 May 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-8360 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-8360/ (Markdown: https://insights.sbomify.com/CVE-2017-8360/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-8360
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-8360
- OSV: https://osv.dev/vulnerability/CVE-2017-8360

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-8360/
Summaries are generated and may contain mistakes; the official description above is the record.