# CVE-2015-5684: Memory corruption in n/a

> A buffer overflow in Lenovo Service Engine allows remote attackers to execute arbitrary code on affected Lenovo notebooks.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 27 Mar 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-xp5w-3gmw-7xvj

## What is CVE-2015-5684?

CVE-2015-5684 is a critical memory corruption vulnerability in n/a, published on 27 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MITRE is populating this ID because it was assigned prior to Lenovo becoming a CNA. A buffer overflow vulnerability was reported, (fixed and publicly disclosed in 2015) in the Lenovo Service Engine (LSE), affecting various versions of BIOS for Lenovo Notebooks, that could allow a remote user to execute arbitrary code on the system.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2015-5684?

It affects 27 products.


Products: Lenovo B50-10 Firmware, Lenovo Edge 15 Firmware, Lenovo Flex 2 Pro-15 Firmware, Lenovo Flex 3-1120 Firmware, Lenovo Flex 3-1470 Firmware, Lenovo Flex 3-1570 Firmware, Lenovo G40-80 Firmware, Lenovo G40-80m Firmware, Lenovo G50-80 Firmware, Lenovo G50-80 Touch Firmware, Lenovo G50-80 Touch V3000 Firmware, Lenovo G50-80m Firmware, Lenovo G70-80 Firmware, Lenovo Ideapad 100-14iby Firmware, Lenovo Ideapad 100-15iby Firmware, Lenovo M40-35 Firmware, Lenovo S21e Firmware, Lenovo S41-70 Firmware, Lenovo S435 Firmware, Lenovo U31-70 Firmware and 7 more.

## How do I fix CVE-2015-5684?

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

## Is CVE-2015-5684 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-5684 and fix it if it is affected.

What it is: CVE-2015-5684 is a critical memory corruption vulnerability in n/a, published on 27 Mar 2020. 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-2015-5684 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-2015-5684/ (Markdown: https://insights.sbomify.com/CVE-2015-5684/index.md)
```

## Sources

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

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