CVE-2024-53651

Filesystem disclosure via unencrypted on-board flash

Published Feb 11, 2025 · Updated Feb 11, 2025

Cleartext storage in Siemens SIPROTEC 5 devices allows physically proximate attackers to read the device filesystem from on-board flash. Certain filesystem data is stored without encryption in flash memory mounted on the device PCB, exposing its contents when the storage is accessed directly. Physical possession of an affected device is required, and the documented consequence is filesystem disclosure without modification or service interruption.

CVSS severity4.6
Medium
EPSS probability0.16%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Cleartext storage in Siemens SIPROTEC 5 devices allows physically proximate attackers to read the device filesystem from on-board flash. Certain filesystem data is stored without encryption in flash memory mounted on the device PCB, exposing its contents when the storage is accessed directly. Physical possession of an affected device is required, and the documented consequence is filesystem disclosure without modification or service interruption.

The record

CVE
CVE-2024-53651
Published
Feb 11, 2025
Updated
Feb 11, 2025
Vendor
Siemens
Product
SIPROTEC 5 7SA87 (CP200)
Classifications
CWE-312
Attack vector
physical
Privileges
unauthenticated

Timeline

How it unfolded

  1. Feb 11, 2025CVE publishedPublication date reported by the CVE source.
  2. Feb 11, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <*

What conditions does exploitation require?

Attack vectorphysical
Required privilegesunauthenticated

What is affected?

Siemens · SIPROTEC 5 7SA87 (CP200)version=0 <*
Siemens · SIPROTEC 5 6MD86 (CP300)version=0 <*
Siemens · SIPROTEC 5 7VK87 (CP200)version=0 <*
Siemens · SIPROTEC 5 7SJ85 (CP300)version=0 <*
Siemens · SIPROTEC 5 7UT85 (CP300)version=0 <*
Siemens · SIPROTEC 5 7SJ82 (CP150)version=0 <*
Siemens · SIPROTEC 5 7SD82 (CP100)version=0 <*
Siemens · SIPROTEC 5 7SA86 (CP300)version=0 <*
Siemens · SIPROTEC 5 7UT82 (CP100)version=0 <*
Siemens · SIPROTEC 5 7SS85 (CP300)version=0 <*
Siemens · SIPROTEC 5 7SJ81 (CP150)version=0 <*
Siemens · SIPROTEC 5 7ST85 (CP200)version=0 <*
Siemens · SIPROTEC 5 7UT85 (CP200)version=0 <*
Siemens · SIPROTEC 5 7VE85 (CP300)version=0 <*
Siemens · SIPROTEC 5 7SL82 (CP100)version=0 <*
Siemens · SIPROTEC 5 7UT87 (CP300)version=0 <*
Siemens · SIPROTEC 5 6MD85 (CP300)version=0 <*
Siemens · SIPROTEC 5 6MD85 (CP200)version=0 <*
Siemens · SIPROTEC 5 7SK85 (CP200)version=0 <*
Siemens · SIPROTEC 5 6MD84 (CP300)version=0 <*
Siemens · SIPROTEC 5 7VU85 (CP300)version=0 <*
Siemens · SIPROTEC 5 6MD89 (CP300)version=0 <*
Siemens · SIPROTEC 5 7ST85 (CP300)version=0 <*
Siemens · SIPROTEC 5 7SD87 (CP200)version=0 <*
Siemens · SIPROTEC 5 Compact 7SX800 (CP050)version=0 <*
Siemens · SIPROTEC 5 7SD86 (CP300)version=0 <*
Siemens · SIPROTEC 5 6MD86 (CP200)version=0 <*
Siemens · SIPROTEC 5 7UM85 (CP300)version=0 <*
Siemens · SIPROTEC 5 7SL87 (CP200)version=0 <*
Siemens · SIPROTEC 5 7SJ81 (CP100)version=0 <*
Siemens · SIPROTEC 5 7SA86 (CP200)version=0 <*
Siemens · SIPROTEC 5 7VK87 (CP300)version=0 <*
Siemens · SIPROTEC 5 7UT87 (CP200)version=0 <*
Siemens · SIPROTEC 5 7SL86 (CP200)version=0 <*
Siemens · SIPROTEC 5 7SL86 (CP300)version=0 <*
Siemens · SIPROTEC 5 7SA87 (CP300)version=0 <*
Siemens · SIPROTEC 5 7SL87 (CP300)version=0 <*
Siemens · SIPROTEC 5 7SJ82 (CP100)version=0 <*
Siemens · SIPROTEC 5 7SJ86 (CP300)version=0 <*
Siemens · SIPROTEC 5 7SS85 (CP200)version=0 <*
Siemens · SIPROTEC 5 7UT82 (CP150)version=0 <*
Siemens · SIPROTEC 5 7SA82 (CP150)version=0 <*
Siemens · SIPROTEC 5 7KE85 (CP200)version=0 <*
Siemens · SIPROTEC 5 7SD82 (CP150)version=0 <*
Siemens · SIPROTEC 5 7SA82 (CP100)version=0 <*
Siemens · SIPROTEC 5 7SL82 (CP150)version=0 <*
Siemens · SIPROTEC 5 6MU85 (CP300)version=0 <*
Siemens · SIPROTEC 5 7SK82 (CP150)version=0 <*
Siemens · SIPROTEC 5 7SX85 (CP300)version=0 <*
Siemens · SIPROTEC 5 7SJ85 (CP200)version=0 <*
Siemens · SIPROTEC 5 7SD86 (CP200)version=0 <*
Siemens · SIPROTEC 5 7UT86 (CP200)version=0 <*
Siemens · SIPROTEC 5 7SJ86 (CP200)version=0 <*
Siemens · SIPROTEC 5 7SK85 (CP300)version=0 <*
Siemens · SIPROTEC 5 7ST86 (CP300)version=0 <*
Siemens · SIPROTEC 5 7SK82 (CP100)version=0 <*
Siemens · SIPROTEC 5 7KE85 (CP300)version=0 <*
Siemens · SIPROTEC 5 7UT86 (CP300)version=0 <*
Siemens · SIPROTEC 5 7SD87 (CP300)version=0 <*
Siemens · SIPROTEC 5 7SX82 (CP150)version=0 <*
Siemens · SIPROTEC 5 7SY82 (CP150)version=0 <*

Published CVSS scores

5.1Siemens ProductCERTCVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
4.6Siemens ProductCERTCVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorphysical
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-312Cleartext Storage of Sensitive Information

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo