# CVE-2017-3740: Other in Active Protection System

> Local attackers can send commands to the embedded controller, causing denial of service or altering hardware functionality in Lenovo Active Protection System.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **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:** 3 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jj4c-v9g6-vg2x

## What is CVE-2017-3740?

CVE-2017-3740 is a medium-severity vulnerability in Lenovo Group Ltd. Active Protection System, published on 3 Jun 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In Lenovo Active Protection System before 1.82.0.14, an attacker with local privileges could send commands to the system's embedded controller, which could cause a denial of service attack on the system or the ability to alter hardware functionality.

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

It affects 1 product.


Products: Lenovo Active Protection System.

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

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

## Is CVE-2017-3740 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-3740 is a medium-severity vulnerability in Lenovo Group Ltd. Active Protection System, published on 3 Jun 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-3740 in the wild and no public exploit code.

Affected product: Lenovo Group Ltd. Active Protection System. 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-3740/ (Markdown: https://insights.sbomify.com/CVE-2017-3740/index.md)
```

## Sources

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

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