# CVE-2017-1000230: Denial of service in n/a

> An attacker can crash the Snap7 Server by sending unexpected input to the ItemCount field in S7 protocol functions, causing a denial of service.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 17 Nov 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-58r9-jqc4-jgp3

## What is CVE-2017-1000230?

CVE-2017-1000230 is a high-severity denial of service vulnerability in n/a, published on 17 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Snap7 Server version 1.4.1 can be crashed when the ItemCount field of the ReadVar or WriteVar functions of the S7 protocol implementation in Snap7 are provided with unexpected input, thus resulting in denial of service attack.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Snap7 Project Snap7 Server.

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

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

## Is CVE-2017-1000230 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-1000230 is a high-severity denial of service vulnerability in n/a, published on 17 Nov 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-1000230 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-1000230/ (Markdown: https://insights.sbomify.com/CVE-2017-1000230/index.md)
```

## Sources

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

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