dbcve.org
Scalance Lpe9403 FirmwareOperating system · Siemens

CVE-2025-40580

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 in SCALANCE LPE9403 devices (all versions prior to V4.0 HF0) allows a non-privileged local attacker to execute arbitrary code or cause a denial of service condition.

MitigationUpgrade SCALANCE LPE9403 firmware to version V4.0 HF0 or later. If immediate upgrade is not possible, restrict physical and local access to affected devices and monitor for indicators of compromise.

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. Identify the device model
    Verify that the target device is a Siemens SCALANCE LPE9403 device. This can be done by checking the device label, web interface, or management console for the model name.
    Affected if The device is a SCALANCE LPE9403 unit.
  2. Determine the installed firmware version
    Access the device's web interface, command-line interface, or management software to retrieve the current firmware version information. Look for a version number such as Vx.x or similar designation.
    Affected if Unable to retrieve firmware version or version displays as anything other than V4.0 HF0 or later.
  3. Compare firmware version to the affected range
    If the firmware version is readable, compare it against V4.0 HF0. Any version designation that is numerically or alphabetically lower than V4.0 HF0 (including V3.x, V2.x, V1.x, or any pre-V4.0 variant) indicates the device is running a vulnerable version.
    Affected if The firmware version is prior to V4.0 HF0.
  4. Verify local access exposure
    Assess whether the device has any local access vectors available to non-privileged users, including physical console access, USB interfaces, or local network services. Check for weak or default credentials on local management interfaces.
    Affected if Non-privileged local access to the device is possible and firmware version is prior to V4.0 HF0.

The device is affected if it is a SCALANCE LPE9403 running firmware version prior to V4.0 HF0 and has accessible local attack vectors.

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 version V4.0 HF0 or later. If immediate upgrade is not possible, restrict physical and local access to affected devices and monitor for indicators of compromise.

Recommended fix Moderate confidence

V4.0 HF0

  1. 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/support)
  2. 2. Review the firmware release notes and installation instructions provided by Siemens before proceeding
  3. 3. Backup the current device configuration if supported by the firmware backup functionality
  4. 4. Upload the V4.0 HF0 firmware to the SCALANCE LPE9403 device using the device's web interface, SIMATIC Step 7, or other Siemens-approved management tools following their documented procedures
  5. 5. Allow the firmware upload and installation process to complete without interruption
  6. 6. After installation, verify the firmware version displays as V4.0 HF0 in the device management interface
  7. 7. Reboot the device if required by the update process or recommended in the release notes
  8. 8. Restore the device configuration from backup if applicable and test device functionality

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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