CVE-2011-4055 json
Buffer overflow in the WebClient ActiveX control in Siemens Tecnomatix FactoryLink 6.6.1 (aka 6.6 SP1), 7.5.217 (aka 7.5 SP2), and 8.0.2.54…
published 2012-01-08 14 y ago modified 2026-06-16 4 mo ago also EUVD-2011-4007
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.6%
- EPSS 4.6% chance of exploitation in 30 days, percentile 91%
- public exploits
- 0
- none known
Summary
Buffer overflow in the WebClient ActiveX control in Siemens Tecnomatix FactoryLink 6.6.1 (aka 6.6 SP1), 7.5.217 (aka 7.5 SP2), and 8.0.2.54 allows remote attackers to execute arbitrary code via a long string in a parameter associated with the location URL.
Patch / fix
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-11-343-01 updated cvss 9.3
Siemens FactoryLink Multiple ActiveX Vulnerabilities
-
Siemens Tecnomatix FactoryLink V8.0.2.54, V7.5.217_V7.5_SP2, V6.6.1_V6.6_SP1affected: mitigation “Customers of vulnerable versions of Siemens Tecnomatix FactoryLink should deploy the Siemens patch. (http://www.usdata.com/sea/factorylink/en/p_nav5.asp)”
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
4.56% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).
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
-
usdata.com
/sea/factorylink/en/p_nav5.asp
patch, vendor-advisory
-
us-cert.gov
/control_systems/pdf/ICSA-11-343-01.pdf
us-government-resource
-
exchange.xforce.ibmcloud.com
/vulnerabilities/72117
vdb-entry
-
securityfocus.com
/bid/51266
vdb-entry
Sources
- CVE List CVE-2011-4055
- NVD CVE-2011-4055
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.