# CVE-2018-8865: Memory corruption in IDS 2102

> A stack-based buffer overflow in Lantech IDS 2102 allows remote attackers to execute arbitrary code without authentication.

- **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:** 4 May 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-rq6r-xw97-qwfr

## What is CVE-2018-8865?

CVE-2018-8865 is a critical memory corruption vulnerability in Lantech IDS 2102, published on 4 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Lantech IDS 2102 2.0 and prior, a stack-based buffer overflow vulnerability has been identified which may allow remote code execution. A CVSS v3 base score of 9.8 has been calculated; the CVSS vector string is (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Weakness: CWE-787 (Out-of-bounds Write), CWE-121 (Stack-based Buffer Overflow)

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

It affects 1 product.


Products: Lantech Ids 2102 Firmware.

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

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

## Is CVE-2018-8865 being exploited?

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

## Other vulnerabilities in Lantech IDS 2102

- [CVE-2018-8869](https://insights.sbomify.com/CVE-2018-8869/): Other in IDS 2102 (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-8865 is a critical memory corruption vulnerability in Lantech IDS 2102, published on 4 May 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-8865 in the wild and no public exploit code.

Affected product: Lantech IDS 2102. 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-8865/ (Markdown: https://insights.sbomify.com/CVE-2018-8865/index.md)
```

## Sources

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

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