CVE-2012-4358 json
Sielco Sistemi Winlog Pro SCADA before 2.07.17 and Winlog Lite SCADA before 2.07.17 do not validate the return value of the realloc functio…
published 2012-08-19 14 y ago modified 2026-06-16 4 mo ago also EUVD-2012-4301
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.5%
- EPSS 2.5% chance of exploitation in 30 days, percentile 84%
- public exploits
- 0
- none known
Summary
Sielco Sistemi Winlog Pro SCADA before 2.07.17 and Winlog Lite SCADA before 2.07.17 do not validate the return value of the realloc function, which allows remote attackers to cause a denial of service (invalid 0x00 write operation and daemon crash) or possibly have unspecified other impact via a port-46824 TCP packet with a crafted positive integer after the opcode.
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.18affected: 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
Exploit prediction
2.52% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- 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-20 Improper Input Validation
References
-
aluigi.org
/adv/winlog_2-adv.txt
exploit
-
secunia.com
/advisories/49395
third-party-advisory, vendor-advisory
-
us-cert.gov
/control_systems/pdf/ICSA-12-213-01.pdf
us-government-resource
- sielcosistemi.com /en/news/index.html?id=69
Sources
- CVE List CVE-2012-4358
- NVD CVE-2012-4358
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.