Skip to content
Fencer Intel
critical 9.3

CVE-2012-4353 in the critical feed json

Stack-based buffer overflow in RunTime.exe in Sielco Sistemi Winlog Pro SCADA before 2.07.17 and Winlog Lite SCADA before 2.07.17 allows re…

published 2012-08-19 14 y ago modified 2026-06-16 4 mo ago also EUVD-2012-4296

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

Summary

Stack-based buffer overflow in RunTime.exe in Sielco Sistemi Winlog Pro SCADA before 2.07.17 and Winlog Lite SCADA before 2.07.17 allows remote attackers to execute arbitrary code via a crafted port-46824 TCP packet that triggers an incorrect file-open attempt by the _TCPIPS_BinOpenFileFP function, a different vulnerability than CVE-2012-3815. NOTE: some of these details are obtained from third party information.

Patch / fix

Vendor advisories

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

cisa ICSA-12-213-01A updated cvss 9.3

Sielco Sistemi Winlog Multiple Vulnerabilities

  • Sielco Sistemi Winlog Lite SCADA <2.07.18. Sielco Sistemi Winlog Pro SCADA <2.07.18
    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-19409)
  2. Published

Exploit prediction

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

Exploits and checks

  • EDB-19409 Sielco Sistemi Winlog 2.07.16 - Multiple Vulnerabilities dos, 2012-06-27
  • aluigi.org http://aluigi.org/adv/winlog_2-adv.txt referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C

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.