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

> A local attacker can trigger buffer overflows in the iscsiuio server via malformed messages, leading to service crashes or arbitrary code execution.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Dec 2017
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2017-17840, GHSA-2mfv-hhmv-9rh8

## What is CVE-2017-17840?

CVE-2017-17840 is a high-severity memory corruption vulnerability in n/a, published on 22 Dec 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in Open-iSCSI through 2.0.875. A local attacker can cause the iscsiuio server to abort or potentially execute code by sending messages with incorrect lengths, which (due to lack of checking) can lead to buffer overflows, and result in aborts (with overflow checking enabled) or code execution. The process_iscsid_broadcast function in iscsiuio/src/unix/iscsid_ipc.c does not validate the payload length before a write operation.

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

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

It affects 1 product.


Products: Open-Iscsi Project Open-Iscsi.

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

Apply the vendor's patch.

## Is CVE-2017-17840 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-17437](https://insights.sbomify.com/CVE-2020-17437/): Memory corruption in n/a (high 8.2)
- [CVE-2020-13987](https://insights.sbomify.com/CVE-2020-13987/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-17840 is a high-severity memory corruption vulnerability in n/a, published on 22 Dec 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-17840 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-17840/ (Markdown: https://insights.sbomify.com/CVE-2017-17840/index.md)
```

## Sources

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

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