# CVE-2017-9945: In the Siemens 7KM PAC Switched Ethernet PROFINET expansion module (All versions < V2.1.3), a Denial-of-Service condition could be induced b


- **Severity:** Medium 6.5 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Aug 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-p785-pc36-p534

## What is CVE-2017-9945?

CVE-2017-9945 is a medium-severity vulnerability in Siemens 7KM PAC Switched Ethernet PROFINET expansion module: All versions < V2.1.3, published on 30 Aug 2017. 

### Official description

In the Siemens 7KM PAC Switched Ethernet PROFINET expansion module (All versions < V2.1.3), a Denial-of-Service condition could be induced by a specially crafted PROFINET DCP packet sent as a local Ethernet (Layer 2) broadcast. The affected component requires a manual restart via the main device to recover.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Siemens 7km Pac Switched Ethernet Profinet Expansion Module Firmware.

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

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

## Is CVE-2017-9945 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-9945 is a medium-severity vulnerability in Siemens 7KM PAC Switched Ethernet PROFINET expansion module: All versions < V2.1.3, published on 30 Aug 2017. 
Exploitation: There is no known exploitation of CVE-2017-9945 in the wild and no public exploit code.

Affected product: Siemens 7KM PAC Switched Ethernet PROFINET expansion module: All versions < V2.1.3. 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-9945/ (Markdown: https://insights.sbomify.com/CVE-2017-9945/index.md)
```

## Sources

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

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