Skip to content
Fencer Intel
medium 5.0

CVE-2012-3792 json

Pro-face WinGP PC Runtime 3.1.00 and earlier, and ProServr.exe in Pro-face Pro-Server EX 1.30.000 and earlier, allows remote attackers to c…

published 2012-06-25 14 y ago modified 2026-06-16 4 mo ago also EUVD-2012-3739

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
10.8%
EPSS 10.8% chance of exploitation in 30 days, percentile 95%
public exploits
1
Exploit-DB

Summary

Pro-face WinGP PC Runtime 3.1.00 and earlier, and ProServr.exe in Pro-face Pro-Server EX 1.30.000 and earlier, allows remote attackers to cause a denial of service (out-of-bounds read operation) via a crafted packet that triggers a certain Find Node check attempt.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-12-179-01 updated cvss 5.8

Pro-Face Pro-Server EX Vulnerabilities

  • Pro-face America, Inc., a subsidiary of Digital Electronics Corporation GP-Pro EX and related software WinGP >=2.00.00, <=3.01.100. Pro-face America, Inc., a subsidiary of Digital Electronics Corporation Pro-Server EX >=1.00.00, <=1.30.00
    affected: mitigation

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

Timeline

  1. First public exploit (EDB-18878)
  2. Published

Exploit prediction

10.80% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-18878 Pro-face Pro-Server EX WinGP PC Runtime - Multiple Vulnerabilities dos, 2012-05-14
  • aluigi.org http://aluigi.org/adv/proservrex_1-adv.txt referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

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.