dbcve.org
Scalance Lpe9403 FirmwareOperating system · Siemens

CVE-2025-40579

HIGH · 7.8 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 →
80/100
Remediation priority · High
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 are vulnerable to a stack-based buffer overflow. This could allow a non-privileged local attacker to execute arbitrary code on the device or to cause a denial of service condition.

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

A stack-based buffer overflow vulnerability exists in SCALANCE LPE9403 devices (6GK5998-3GS00-2AC2) running firmware versions prior to V4.0 HF0. This memory corruption flaw allows a non-privileged local attacker to overwrite stack memory and potentially achieve arbitrary code execution or trigger a denial of service condition on the affected industrial network device.

MitigationApply the vendor-supplied firmware update to version V4.0 HF0 or later. Prior to deployment, validate the update in a staging environment to ensure compatibility with the operational industrial network. Limit physical and local network access to affected devices to reduce attack surface.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checks

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

  1. Confirm device model is SCALANCE LPE9403
    Inspect the device hardware label or access the device web management interface to verify the model number matches 6GK5998-3GS00-2AC2
    Affected if Device model is SCALANCE LPE9403 with part number 6GK5998-3GS00-2AC2
  2. Locate firmware version information
    Access the device web interface, command line interface, or management console and navigate to the system information or firmware version display area
    Affected if Firmware version cannot be determined or is not visible
  3. Compare installed firmware version against V4.0 HF0
    Document the current firmware version number displayed in the device management interface or CLI output, then compare it to the fixed version V4.0 HF0
    Affected if Firmware version is any version prior to V4.0 HF0 (including all legacy versions, beta releases, and interim updates)
  4. Verify vulnerability is locally exploitable
    Confirm the device is accessible via local physical ports or local network segments, as the CVE describes a local attack vector
    Affected if Device has local physical access or local network accessibility for non-privileged users

A SCALANCE LPE9403 device is affected if it is the 6GK5998-3GS00-2AC2 model and runs any firmware version earlier than V4.0 HF0.

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

Apply the vendor-supplied firmware update to version V4.0 HF0 or later. Prior to deployment, validate the update in a staging environment to ensure compatibility with the operational industrial network. Limit physical and local network access to affected devices to reduce attack surface.

Recommended fix High confidence

V4.0 HF0

  1. 1. Identify the current firmware version of the SCALANCE LPE9403 device (6GK5998-3GS00-2AC2) by accessing the device management interface or checking the firmware file currently installed.
  2. 2. Compare the current version against V4.0 HF0 - any version below V4.0 HF0 is affected by the stack-based buffer overflow vulnerability.
  3. 3. Obtain the fixed firmware version V4.0 HF0 (or later) from the official Siemens download portal at cert-portal.siemens.com or through your authorized Siemens support channel.
  4. 4. Follow Siemens' standard firmware update procedure for the SCALANCE LPE9403 device to apply the V4.0 HF0 firmware upgrade.
  5. 5. After upgrading, verify that the device is running firmware version V4.0 HF0 or higher and confirm normal operation.

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

Fix this in Scalance Lpe9403 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA6.0 h
28.0 hours of engineering $4,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-40579 — 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-40579 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