CVE-2016-2292 json
Stack-based buffer overflow in Pro-face GP-Pro EX EX-ED before 4.05.000, PFXEXEDV before 4.05.000, PFXEXEDLS before 4.05.000, and PFXEXGRPL…
published 2016-04-06 10 y ago modified 2026-06-17 4 mo ago also EUVD-2016-3376
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.3%
- EPSS 2.3% chance of exploitation in 30 days, percentile 83%
- public exploits
- 0
- none known
Summary
Stack-based buffer overflow in Pro-face GP-Pro EX EX-ED before 4.05.000, PFXEXEDV before 4.05.000, PFXEXEDLS before 4.05.000, and PFXEXGRPLS before 4.05.000 allows remote attackers to execute arbitrary code via unspecified vectors.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-16-096-01 updated cvss 6.5
Pro-face GP-Pro EX HMI Vulnerabilities
-
Pro-face EX-ED >=1.00, <4.0.4 Pro-face PFXEXEDLS >=1.00, <4.0.4 Pro-face PFXEXEDV >=1.00, <4.0.4 Pro-face PFXEXGRPLS >=1.00, <4.0.4affected: mitigation “Pro-face has released the following module: GP-Pro EX (Ver. 4.05.000 or later). The Update Module includes: Editor: Ver.4.05.000, Transfer Tool: Ver.4.05.000, and System/Runtime: Ver.4.5.0”
From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf
Exploit prediction
2.33% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
ics-cert.us-cert.gov
/advisories/ICSA-16-096-01
third-party-advisory, us-government-resource
Sources
- CVE List CVE-2016-2292
- NVD CVE-2016-2292
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.