# CVE-2016-8377: Memory corruption in Fatek Automation PLC WinProladder 3.11 Build 14701

> A stack-based buffer overflow in Fatek WinProladder allows remote code execution when connecting to a malicious server.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Feb 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-pjr3-5p2r-73h6

## What is CVE-2016-8377?

CVE-2016-8377 is a high-severity memory corruption vulnerability in Fatek Automation PLC WinProladder 3.11 Build 14701, published on 13 Feb 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

An issue was discovered in Fatek Automation PLC WinProladder Version 3.11 Build 14701. A stack-based buffer overflow vulnerability exists when the software application connects to a malicious server, resulting in a stack buffer overflow. This causes an exploitable Structured Exception Handler (SEH) overwrite condition that may allow remote code execution.

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

## Which versions are affected by CVE-2016-8377?

It affects 1 product.


Products: Fatek Plc Winproladder Firmware.

## How do I fix CVE-2016-8377?

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

## Is CVE-2016-8377 being exploited?

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

Public exploit code:

- Fatek Automation PLC WinProladder 3.11 Build 14701 - Stack Buffer Overflow (Metasploit) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-8377 and fix it if it is affected.

What it is: CVE-2016-8377 is a high-severity memory corruption vulnerability in Fatek Automation PLC WinProladder 3.11 Build 14701, published on 13 Feb 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-8377 in the wild and no public exploit code.

Affected product: Fatek Automation PLC WinProladder 3.11 Build 14701. 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-2016-8377/ (Markdown: https://insights.sbomify.com/CVE-2016-8377/index.md)
```

## Sources

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

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