# CVE-2018-17174: Memory corruption in n/a

> A stack-based buffer overflow in the nmealib library allows attackers to cause denial of service or potentially execute arbitrary code via malformed data.

- **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:** 21 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-j3vp-r32p-2w3f

## What is CVE-2018-17174?

CVE-2018-17174 is a critical memory corruption vulnerability in n/a, published on 21 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A stack-based buffer overflow was discovered in the xtimor NMEA library (aka nmealib) 0.5.3. nmea_parse() in parser.c allows an attacker to trigger denial of service (even arbitrary code execution in a certain context) in a product using this library via malformed data.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Nmealib Project Nmealib.

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

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

## Is CVE-2018-17174 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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