Skip to content
Fencer Vulns
high 7.5

CVE-2019-13925 json

A vulnerability has been identified in SCALANCE S602 (All versions >= V3.0 and < V4.1), SCALANCE S612 (All versions >= V3.0 and < V4.1), SC…

published 2020-02-11 6 y ago modified 2026-06-17 4 mo ago also EUVD-2019-5195

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

Summary

A vulnerability has been identified in SCALANCE S602 (All versions >= V3.0 and < V4.1), SCALANCE S612 (All versions >= V3.0 and < V4.1), SCALANCE S623 (All versions >= V3.0 and < V4.1), SCALANCE S627-2M (All versions >= V3.0 and < V4.1). Specially crafted packets sent to port 443/tcp of affected devices could cause a Denial-of-Service condition of the web server.

Patch / fix

  • siemens scalance_s602_firmware 4.1
  • siemens scalance_s612_firmware 4.1
  • siemens scalance_s623_firmware 4.1
  • siemens scalance_s627-2m_firmware 4.1

Vendor advisories

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

cisa ICSA-20-042-10 updated cvss 7.5

Siemens SCALANCE S-600 (Update B)

  • Siemens SCALANCE S602 >=V3.0_and_<V4.1 Siemens SCALANCE S612 >=V3.0_and_<V4.1 Siemens SCALANCE S623 >=V3.0_and_<V4.1 Siemens SCALANCE S627-2M >=V3.0_and_<V4.1
    affected: fixed in V4.1, 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

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

CVSS scores

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

Affected products

  • Siemens SCALANCE S602
  • Siemens SCALANCE S612
  • Siemens SCALANCE S623
  • Siemens SCALANCE S627-2M

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption

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.