# CVE-2024-7013: Memory corruption in Control FPWIN Pro

> Attackers can execute arbitrary code by tricking users into opening a specially crafted project file in Control FPWIN Pro.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Aug 2024
- **Updated:** 21 Aug 2024
- **Also known as:** GHSA-37fw-j45g-2rh2

## What is CVE-2024-7013?

CVE-2024-7013 is a high-severity memory corruption vulnerability in Panasonic Holdings Corporation Control FPWIN Pro, published on 21 Aug 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Stack-based buffer overflow in Control FPWIN Pro version 7.7.2.0 and all previous versions may allow attackers to execute arbitrary code via a specially crafted project file.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2024-7013?


## How do I fix CVE-2024-7013?

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

## Is CVE-2024-7013 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-7013 and fix it if it is affected.

What it is: CVE-2024-7013 is a high-severity memory corruption vulnerability in Panasonic Holdings Corporation Control FPWIN Pro, published on 21 Aug 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-7013 in the wild and no public exploit code.

Affected product: Panasonic Holdings Corporation Control FPWIN Pro. 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-2024-7013/ (Markdown: https://insights.sbomify.com/CVE-2024-7013/index.md)
```

## Sources

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

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