Skip to content
Fencer Intel
medium 5.0

CVE-2011-4530 json

Siemens Automation License Manager (ALM) 4.0 through 5.1+SP1+Upd1 does not properly copy fields obtained from clients, which allows remote…

published 2012-01-08 14 y ago modified 2026-06-16 4 mo ago also EUVD-2011-4456

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

Summary

Siemens Automation License Manager (ALM) 4.0 through 5.1+SP1+Upd1 does not properly copy fields obtained from clients, which allows remote attackers to cause a denial of service (exception and daemon crash) via long fields, as demonstrated by fields to the (1) open_session->workstation->NAME or (2) grant->VERSION function.

Vendor advisories

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

cisa ICSA-11-361-01 updated cvss 5.0

Siemens Automation License Manager Vulnerabilities

  • Siemens Automation License Manager >=4.0, <5.1+SP1+Upd1, >=2.0, <5.1+SP1+Upd2
    affected: mitigation “Customers of vulnerable versions of Siemens ALM should deploy the Siemens patch that Siemens sent out to its customers.”

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

Exploit prediction

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

Exploits and checks

  • EDB-18165 siemens automation license manager 500.0.122.1 - Multiple Vulnerabilities dos, 2011-11-28
  • aluigi.altervista.org http://aluigi.altervista.org/adv/almsrvx_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-20 Improper Input Validation

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.