Skip to content
Fencer Intel
high 7.4

CVE-2017-2685 json

Siemens SINUMERIK Integrate Operate Clients between 2.0.3.00.016 (including) and 2.0.6 (excluding) and between 3.0.4.00.032 (including) and…

published 2017-03-01 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-11828

cvss
7.4
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 62%
public exploits
0
none known

Summary

Siemens SINUMERIK Integrate Operate Clients between 2.0.3.00.016 (including) and 2.0.6 (excluding) and between 3.0.4.00.032 (including) and 3.0.6 (excluding) contain a vulnerability that could allow an attacker to read and manipulate data in TLS sessions while performing a man-in-the-middle (MITM) attack.

Vendor advisories

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

cisa ICSA-17-061-03 updated cvss 7.4

Siemens SINUMERIK Integrate and SINUMERIK Operate

  • Siemens SINUMERIK Integrate Access MyMachine/Ethernet with AMM Service Engineer Client (ActiveX) Siemens SINUMERIK Integrate Operate client 4.5, SP6 (including) and V4.5 SP6 Hotfix 8 (excluding), 4.7, SP2 Hotfix 1 (including) and V4.7 SP4 (excluding) Siemens SINUMERIK Integrate Operate Client 2.0.3.00.016 (including) and 2.0.6 (excluding), 3.0.4.00.032 (including) and 3.0.6 (excluding)
    affected: vendor fix w3.siemens.com

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

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

CVSS scores

assigned by version score vector
NVD 3.0 7.4 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
NVD 2.0 5.8 AV:N/AC:M/Au:N/C:P/I:P/A:N

Affected products

  • n/a SINUMERIK Integrate Operate Clients 2.x and 3.x

Classification

Weakness
  • CWE-693 Protection Mechanism Failure
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

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.