Skip to content
Fencer Intel
medium 6.6

CVE-2019-10928 json

A vulnerability has been identified in SCALANCE SC-600 (V2.0).

published 7y ago modified 4mo ago also EUVD-2019-2642

cvss
6.6
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 35%
public exploits
0
none known

Summary

A vulnerability has been identified in SCALANCE SC-600 (V2.0). An authenticated attacker with access to port 22/tcp as well as physical access to an affected device may trigger the device to allow execution of arbitrary commands. The security vulnerability could be exploited by an authenticated attacker with physical access to the affected device. No user interaction is required to exploit this vulnerability. The vulnerability impacts the confidentiality, integrity and availability of the affected device.

Is CVE-2019-10928 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

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

cisa ICSA-19-227-03 updated cvss 6.6

Siemens SCALANCE Products (Update A)

  • Siemens SCALANCE SC-600 V2.0
    affected: fixed in V2.0.1, mitigation
  • Siemens SCALANCE XB-200 V4.1 Siemens SCALANCE XC-200 V4.1 Siemens SCALANCE XF-200BA V4.1 Siemens SCALANCE XP-200 V4.1 Siemens SCALANCE XR-300WG V4.1
    affected: fixed in V4.2, mitigation

Facts from CISA's republication of the vendor's own advisory (CSAF); the linked advisory is the authoritative source. CISA notification · csaf

Exploit prediction

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

CVSS scores

assigned by version score vector
NVD 3.1 6.6 CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 4.6 AV:L/AC:L/Au:N/C:P/I:P/A:P

Affected products

  • Siemens AG SCALANCE SC-600

Classification

Weakness
  • CWE-703 Improper Check or Handling of Exceptional Conditions

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.