# CVE-2016-4499: Heap-based buffer overflow in Panasonic FPWIN Pro 5.x through 7.x before 7.130 allows local users to cause a denial of service (application


- **Severity:** Medium 4.2 (`CVSS:3.0/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 12 May 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-9q67-fpxq-mm5h

## What is CVE-2016-4499?

CVE-2016-4499 is a medium-severity vulnerability in n/a, published on 12 May 2016. 

### Official description

Heap-based buffer overflow in Panasonic FPWIN Pro 5.x through 7.x before 7.130 allows local users to cause a denial of service (application crash) via unspecified vectors.

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

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

It affects 1 product.


Products: Panasonic Fpwin Pro.

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

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

## Is CVE-2016-4499 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-6314](https://insights.sbomify.com/CVE-2023-6314/): Memory corruption in Control FPWIN Pro (high 7.8)
- [CVE-2023-6315](https://insights.sbomify.com/CVE-2023-6315/): Memory corruption in Control FPWIN Pro (high 7.8)
- [CVE-2020-16236](https://insights.sbomify.com/CVE-2020-16236/): anasonic FPWIN Pro (high 7.8)
- [CVE-2021-32972](https://insights.sbomify.com/CVE-2021-32972/): XML external entity in Panasonic FPWIN Pro (medium 5.5)
- [CVE-2016-4498](https://insights.sbomify.com/CVE-2016-4498/): Null dereference in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-4499 is a medium-severity vulnerability in n/a, published on 12 May 2016. 
Exploitation: There is no known exploitation of CVE-2016-4499 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-2016-4499/ (Markdown: https://insights.sbomify.com/CVE-2016-4499/index.md)
```

## Sources

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

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