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

> A stack-based buffer overflow in RIOT OS allows attackers to cause a denial of service via a malformed IPv6 address.

- **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:** 27 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-hcv8-7fjm-9wh2

## What is CVE-2017-8289?

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

### Official description

Stack-based buffer overflow in the ipv6_addr_from_str function in sys/net/network_layer/ipv6/addr/ipv6_addr_from_str.c in RIOT prior to 2017-04-25 allows local attackers, and potentially remote attackers, to cause a denial of service or possibly have unspecified other impact via a malformed IPv6 address.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Riot Project Riot.

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

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

## Is CVE-2017-8289 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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