# CVE-2017-18681: Memory corruption in n/a

> Buffer overflows in the Samsung Galaxy S5 bootloader allow attackers to execute arbitrary code and escalate privileges.

- **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:** 7 Apr 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-cw6r-hw8g-cx8v

## What is CVE-2017-18681?

CVE-2017-18681 is a critical memory corruption vulnerability in n/a, published on 7 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on Samsung Galaxy S5 mobile devices with software through 2016-12-20 (Qualcomm AP chipsets). There are multiple buffer overflows in the bootloader. The Samsung ID is SVE-2016-7930 (March 2017).

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

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

It affects 1 product.


Products: Samsung Galaxy S5 Firmware.

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

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

## Is CVE-2017-18681 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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