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.
Product
panasonic Control FPWIN Pro vulnerabilities
8 published CVES affecting panasonic Control FPWIN Pro, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 8
- Critical
- 0
- High
- 8
- Medium
- 0
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest panasonic Control FPWIN Pro CVEs
Newest publication first
-
HighCVSS 7.8 EPSS 0.28%
-
HighCVSS 7.8 EPSS 0.27%
Out-of-bouds read vulnerability in FPWin Pro version 7.7.0.0 and all previous versions may allow attackers to execute arbitrary code via a specially crafted project file.
-
HighCVSS 7.8 EPSS 0.27%
Stack-based buffer overflow in FPWin Pro version 7.7.0.0 and all previous versions may allow attackers to execute arbitrary code via a specially crafted project file.
-
HighCVSS 7.8 EPSS 0.21%
A memory corruption vulnerability Panasonic Control FPWIN Pro versions 7.6.0.3 and all previous versions may allow arbitrary code execution when opening specially crafted project files.
-
HighCVSS 7.8 EPSS 0.21%
A type confusion vulnerability in Panasonic Control FPWIN Pro versions 7.6.0.3 and all previous versions may allow arbitrary code execution when opening specially crafted project files.
-
HighCVSS 7.8 EPSS 0.28%
A stack-based buffer overflow in Panasonic Control FPWIN Pro versions 7.6.0.3 and all previous versions may allow arbitrary code execution when opening specially crafted project files.
-
HighCVSS 7.8 EPSS 3.8%
Panasonic FPWIN Pro version 7.3.0.0 and prior allows attacker-created project files to be loaded by an authenticated user triggering incompatible type errors because the resource does not have expected properties. This may lead to remote code execution.
-
HighCVSS 7.8 EPSS 6.9%
Panasonic FPWIN Pro version 7.3.0.0 and prior allows attacker-created project files to be loaded by an authenticated user causing heap-based buffer overflows, which may lead to remote code execution.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.