CVE-2019-13925
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA stack-based buffer overflow vulnerability in the web server of Siemens SCALANCE S602, S612, S623, and S627-2M industrial network devices (versions V3.0 through <V4.1) allows remote attackers to cause a Denial-of-Service condition by sending specially crafted packets to port 443/tcp. The vulnerability is exploitable remotely without authentication (CVSS:7.5 HIGH).
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 3.0, < 4.1>= 3.0, < 4.1>= 3.0, < 4.1>= 3.0, < 4.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the SCALANCE device modelAccess the device web interface or use SNMP/CLI to retrieve the hardware model designation (S602, S612, S623, or S627-2M).Affected if The device model is not one of these four models.
-
Retrieve the installed firmware versionLog into the device web interface, CLI, or use SNMP to query the firmware version. Common paths: Device Overview page in web UI, 'show version' command in CLI, or SNMP OID for firmware revision.Affected if The firmware version cannot be determined or retrieved.
-
Compare firmware version against affected rangeCompare the retrieved firmware version to the affected range: versions greater than or equal to V3.0 but less than V4.1 are vulnerable. Versions V4.1 and later are not affected.Affected if Firmware version is V3.0 through V4.0.x (any version less than V4.1).
-
Verify web server accessibility on port 443Attempt a TCP connection to port 443 on the device IP address (e.g., using telnet, nc, or nmap). If the connection succeeds and a web server responds, the vulnerable service is exposed.Affected if Port 443/tcp is open and the web server is reachable from the network.
The device is affected if it is a SCALANCE S602, S612, S623, or S627-2M running firmware V3.0 through V4.0.x and has the web server on port 443 accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data4.1
Upgrade SCALANCE S-series devices to firmware version V4.1 or later to remediate this vulnerability. If immediate patching is not feasible, consider restricting network access to port 443/tcp on affected devices.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-13925 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-13925 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data