Skip to content
Fencer Intel
critical 10.0

CVE-2012-5409 in the critical feed json

AscoServer.exe in the server in Siemens SiPass integrated MP2.6 and earlier does not properly handle IOCP RPC messages received over an Eth…

published 2012-11-01 14 y ago modified 2026-06-16 4 mo ago also EUVD-2012-5328

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

Summary

AscoServer.exe in the server in Siemens SiPass integrated MP2.6 and earlier does not properly handle IOCP RPC messages received over an Ethernet network, which allows remote attackers to write data to any memory location and consequently execute arbitrary code via crafted messages, as demonstrated by an arbitrary pointer dereference attack or a buffer overflow attack.

Vendor advisories

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

cisa ICSA-12-305-01 updated cvss 10.0

Siemens SiPass Server Buffer Overflow

  • Siemens SiPass integrated <=MP2.6
    affected: mitigation “The affected software components are implemented under the assumption of running in a protected IT environment. Siemens strongly recommends protecting systems according to common security practices.”

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-22397)
  2. Published

Exploit prediction

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

Exploits and checks

  • EDB-22397 SIEMENS Sipass Integrated 2.6 Ethernet Bus - Arbitrary Pointer Dereference dos, 2012-11-01

CVSS scores

assigned by version score vector
NVD 2.0 10.0 AV:N/AC:L/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.