dbcve.org
Scalance Lpe9403 FirmwareOperating system · Siemens

CVE-2025-40575

MEDIUM · 5.3 CVSS v3.1 Published 2025-05-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability has been identified in SCALANCE LPE9403 (6GK5998-3GS00-2AC2) (All versions < V4.0 HF0). Affected devices do not properly validate incoming Profinet packets. An unauthenticated remote attacker can exploit this flaw by sending a specially crafted malicious packet, which leads to a crash of the dcpd process.

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 confidence

The SCALANCE LPE9403 industrial network device contains a vulnerability in the dcpd (Discovery and Configuration Protocol daemon) process where incoming Profinet packets are not properly validated. An unauthenticated remote attacker can send specially crafted malicious packets to crash the dcpd process, resulting in denial of service.

MitigationUpgrade SCALANCE LPE9403 firmware to V4.0 HF0 or later to remediate this vulnerability. As an interim measure, consider network segmentation to restrict unauthorized Profinet traffic to affected devices.

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
Scalance Lpe9403 FirmwareOperating system
Affected:all versions

CVSS 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
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Access the device web interface, CLI, or management console and confirm the model is SCALANCE LPE9403. Check device nameplate, system info, or SNMP sysDescr.
    Affected if Device is confirmed as SCALANCE LPE9403
  2. Check firmware version
    In the device web interface, go to System > Firmware or use CLI command 'show firmware version' or 'show system info'. Note the exact firmware version string.
    Affected if Firmware version is any version prior to V4.0 HF0, or version cannot be determined (all versions are affected)
  3. Verify dcpd process is running
    Access device CLI and run 'show processes' or 'ps aux | grep dcpd' to check if the Discovery and Configuration Protocol daemon (dcpd) is currently active.
    Affected if dcpd process is running (vulnerability requires dcpd to be active to accept Profinet packets)
  4. Confirm Profinet functionality is enabled
    In the web interface under Ports or Network Settings, check if Profinet or DCP functions are enabled. On CLI, run 'show dcp' or check configuration for 'profinet' or 'dcp' settings.
    Affected if Profinet or DCP discovery is enabled and accepting traffic
  5. Check for crash indicators
    Review device logs or run 'show log' in CLI. Look for entries indicating dcpd process crashes, restarts, or segfaults, especially with timestamps matching suspicious network activity.
    Affected if Recent dcpd crashes or unexpected restarts are logged

The device is affected if it is an SCALANCE LPE9403 with firmware prior to V4.0 HF0, has dcpd running, and has Profinet/DCP enabled to accept incoming network packets.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade SCALANCE LPE9403 firmware to V4.0 HF0 or later to remediate this vulnerability. As an interim measure, consider network segmentation to restrict unauthorized Profinet traffic to affected devices.

Recommended fix Moderate confidence

V4.0 HF0

  1. Obtain the V4.0 HF0 firmware update for SCALANCE LPE9403 (6GK5998-3GS00-2AC2) from the official Siemens support portal (cert-portal.siemens.com or siemens.com)
  2. Follow Siemens standard firmware upgrade procedures for the SCALANCE LPE9403 device to apply V4.0 HF0

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Scalance Lpe9403 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-40575 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-40575 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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