Skip to content
Fencer Vulns
medium 5.9

CVE-2020-28395 json

A vulnerability has been identified in SCALANCE X-200RNA switch family (All versions < V3.2.7), SCALANCE X-300 switch family (incl.

published 2021-01-12 5 y ago modified 2026-06-17 4 mo ago also EUVD-2020-20854

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

Summary

A vulnerability has been identified in SCALANCE X-200RNA switch family (All versions < V3.2.7), SCALANCE X-300 switch family (incl. X408 and SIPLUS NET variants) (All versions < V4.1.0). Devices do not create a new unique private key after factory reset. An attacker could leverage this situation to a man-in-the-middle situation and decrypt previously captured traffic.

Patch / fix

  • siemens scalance_xr324-12m_firmware 4.1.0
  • siemens scalance_xr324-12m_ts_firmware 4.1.0
  • siemens scalance_xr324-4m_eec_firmware 4.1.0
  • siemens scalance_xr324-4m_poe_firmware 4.1.0
  • siemens scalance_xr324-4m_poe_ts_firmware 4.1.0
  • siemens scalance_xr324wg_firmware 4.1.0
  • siemens scalance_xr326-2c_poe_wg_firmware 4.1.0
  • siemens scalance_xr328-4c_wg_firmware 4.1.0

Vendor advisories

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

cisa ICSA-21-012-02 updated cvss 9.1

Siemens SCALANCE X Switches (Update B)

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

Exploit prediction

1.19% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

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

Affected products

  • Siemens SCALANCE X-200RNA switch family
  • Siemens SCALANCE X-300 switch family (incl. X408 and SIPLUS NET variants)

Classification

Weakness
  • CWE-321 Use of Hard-coded Cryptographic Key
  • CWE-798 Use of Hard-coded Credentials

References

Sources

Fencer Vulns 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.