# CVE-2018-3641: Privilege escalation in Intel Remote Keyboard

> A network attacker can inject keystrokes to escalate privileges to a local user in Intel Remote Keyboard.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Apr 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-4rcw-rqxp-x962

## What is CVE-2018-3641?

CVE-2018-3641 is a critical vulnerability in Intel Remote Keyboard, published on 3 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Escalation of privilege in all versions of the Intel Remote Keyboard allows a network attacker to inject keystrokes as a local user.

## Which versions are affected by CVE-2018-3641?

It affects 1 product.


Products: Intel Remote Keyboard Mobile App.

## How do I fix CVE-2018-3641?

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

## Is CVE-2018-3641 being exploited?

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

## Other vulnerabilities in Intel Remote Keyboard

- [CVE-2018-3638](https://insights.sbomify.com/CVE-2018-3638/): Privilege escalation in Intel Remote Keyboard (high 7.8)
- [CVE-2018-3645](https://insights.sbomify.com/CVE-2018-3645/): Privilege escalation in Intel Remote Keyboard (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-3641 and fix it if it is affected.

What it is: CVE-2018-3641 is a critical vulnerability in Intel Remote Keyboard, published on 3 Apr 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-3641 in the wild and no public exploit code.

Affected product: Intel Remote Keyboard. 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-2018-3641/ (Markdown: https://insights.sbomify.com/CVE-2018-3641/index.md)
```

## Sources

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

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