CVE-2024-32014VulnerabilityPublished 11 Nov 2025Updated 12 Nov 2025

CVE-2024-32014: Siemens Spectrum Power 4 · Incorrect Permissions

Affects Siemens Spectrum Power 4Source CVE Database V5

Not known to be exploited · CVSS 4.7 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

4.7Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Local
Attack Complexity: High
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Siemens Spectrum Power 4	Affected =0	Fixed in–

AI-suggested

1. Apply Siemens Spectrum Power 4 updates immediately once V4.70 SP12 Update 2 or later versions are available to patch the vulnerability. 2. Restrict local access to systems running Spectrum Power 4 strictly to authorized and trusted personnel only. 3. Implement robust endpoint security controls on machines with local access to prevent unauthorized user interaction or malware execution. 4. Monitor the local database files for unauthorized changes using file integrity monitoring tools. 5. Employ network segmentation to isolate critical control systems and limit lateral movement opportunities. 6. Conduct regular audits of user privileges and access logs to detect suspicious activities. 7. Train staff on the risks of local privilege escalation and enforce strict physical security controls around critical infrastructure equipment. 8. Prepare incident response plans specifically addressing potential insider threats and local privilege escalation scenarios.

Description

A vulnerability has been identified in Spectrum Power 4 (All versions < V4.70 SP12 Update 2). The affected application is vulnerable to alter the local database which contains the application credentials. This allows an attacker to gain administrative application privileges.

Impact

For European organizations, particularly those in the energy and utilities sectors relying on Siemens Spectrum Power 4, this vulnerability could lead to unauthorized administrative access to critical grid management systems. Such access could allow attackers to manipulate operational parameters, disrupt energy distribution, or exfiltrate sensitive credential data. Although exploitation requires local access and user interaction, insider threats or compromised local machines could leverage this flaw to escalate privileges. The impact on confidentiality is significant due to exposure of credentials, which could cascade into broader system compromise. Given the strategic importance of energy infrastructure in Europe, successful exploitation could affect national grid stability and energy supply continuity. The medium CVSS score reflects mitigated risk by access requirements, but the critical nature of affected systems elevates the potential consequences. Organizations may face regulatory scrutiny and operational disruptions if this vulnerability is exploited.

CWE-732Incorrect Permission Assignment for Critical Resource (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
Implementation
When using a critical resource such as a configuration file, check to see if the resource has insecure permissions (such as being modifiable by any regular user), and generate an error or even exit the software if there is a possibility that the resource could have been modified by an unauthorized party.
Architecture and Design
Divide the software into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully defining distinct user groups, privileges, and/or roles. Map these against data, functionality, and the related resources. Then set the permissions accordingly.
Architecture and Design · Operation · Sandbox or Jail
Run the code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software.
OWASP Cheat Sheets
REST Assessment (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V4.3.3 (opens in a new tab)
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
Directory Indexing (opens in a new tab)
Using Malicious Files (opens in a new tab)
Exploiting Incorrectly Configured Access Control Security Levels (opens in a new tab)
Signing Malicious Code (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

cert-portal.siemens.com/productcert/html/ssa-339694.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 18 Nov 2025, 22:36 UTC

WeaknessesCWE-732

Technical details

References

Community reviews

Related threats