Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessPosition as malicious/MITM S7 webserver
-
DeliveryClient initiates ticket download
-
ExploitReturn response with traversal filename
-
ExecutionClient writes file outside download dir
-
ImpactOverwrite application-accessible file
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK
2 techniques across 2 tactics: Discovery, Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the attacker to control or man-in-the-middle the remote server from which the .NET client performs a ticket download, so that the attacker can supply a crafted filename in the ticket response - the client does not validate this filename before writing. The arbitrary-file-WRITE outside the download directory occurs on any affected version; the additional ability to REPLACE existing files is limited to deployments where the application has file overwriting enabled. Key limiting factors: the vulnerable component is a client library (not a listening service), so the attacker must already sit in the server/MITM position relative to the victim client, and the file-overwrite escalation depends on the non-default overwrite setting. |
| Impact | This is a CWE-22 path traversal in a Siemens-published .NET client library (all versions < V3.3.61) that improperly validates filenames returned by a remote server during ticket downloads, enabling arbitrary file write outside the intended directory. Siemens' CVSS 4.0 vector (AV:N/AC:L/PR:N/UI:N) scores it 8.7 (High) with impact concentrated entirely on integrity (VI:H; VC:N/VA:N) - consistent with a file-write primitive that could overwrite application-accessible files and plausibly lead to code execution, though the advisory does not claim RCE. A critical nuance the raw vector obscures: this is a CLIENT library, so exploitation requires an attacker who already controls or can MITM the server the client connects to ('an attacker who can manipulate the ticket response'). This is not a classic server-side remote-unauthenticated bug against a listening service, despite the AV:N/PR:N framing. No EPSS score, CISA KEV listing, or public POC is present in the provided data - so there is no evidence of active or imminent exploitation. Net assessment: a genuinely serious flaw for environments where the library connects to untrusted or MITM-able S7 webserver endpoints, but real-world urgency is tempered by the niche OT deployment footprint and the server-control precondition. Prioritize patching to V3.3.61 for affected integrations, but this is not a drop-everything internet-wide threat. |
| Exploit ScenarioDerived | An attacker who controls a malicious or compromised SIMATIC S7 webserver (or who can man-in-the-middle the connection) returns a ticket-download response containing a crafted filename with directory-traversal sequences. The vulnerable .NET client writes the downloaded content to an attacker-chosen path outside the intended download directory, and where overwriting is enabled, replaces an existing file the application can access - potentially a binary or config leveraged for code execution. No public exploit code is identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv3 – Oct 13, 2026
Path traversal in the Siemens .NET Client Library for the SIMATIC S7 Webserver API (all versions prior to V3.3.61) lets a remote attacker who controls or man-in-the-middles the server that the client downloads tickets from specify a crafted filename and thereby write arbitrary files outside the intended download directory. Integrity impact is high (VI:H) while confidentiality and availability impacts are none, consistent with the vendor's CVSS 4.0 base score of 8.7; the CVSS vector indicates no privileges (PR:N) or user interaction (UI:N) are required, so the only real prerequisite is that the attacker already occupies the server/MITM position relative to the victim client. The additional ability to replace existing files is limited to deployments where file overwriting is enabled. No public exploit code was identified at time of analysis and there is no indication of confirmed active exploitation.
Earlier versions of this analysis (2)
Path traversal in the Siemens .NET Client Library for SIMATIC S7 Webserver API (versions before V3.3.61) allows an unauthenticated attacker who can control or intercept a ticket-download response to write arbitrary files outside the intended download directory. If the application has enabled the overwriting option, existing files accessible to the application can be replaced. Exploitation requires a malicious or compromised SIMATIC S7 Webserver endpoint or a man-in-the-middle position; no public exploit identified at time of analysis, and the vendor has released V3.3.61 to address the flaw.
Path traversal in the .NET Client Library for SIMATIC S7 Webserver API (all versions before V3.3.61) allows an attacker who can control a ticket-download response to write arbitrary files outside the intended download directory, and to replace existing files when the consuming application has file-overwriting enabled. The vulnerable code is client-side: exploitation requires the attacker to operate a malicious SIMATIC S7 webserver, compromise a legitimate one, or hold a man-in-the-middle position on the affected client's connection, with no authentication required (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N, assessed). No public exploit code and no confirmed active exploitation were identified at time of analysis, and because the flaw lives in a library, impact is bounded to hosts running an application built on versions below V3.3.61 that connect to attacker-influenced servers rather than to any self-contained remote attack surface.
RemediationAI
Vendor-released patch: upgrade the .NET Client Library for SIMATIC S7 Webserver API to V3.3.61 or later, which adds proper validation of filenames received in ticket responses; distribute the updated library to every application that embeds it, not just to the primary deployment. If upgrading immediately is not possible, the most effective compensating control is to disable file overwriting in the client configuration, which removes the file-replacement capability (a non-default behavior) but does not prevent the underlying arbitrary write outside the download directory, so it should be treated as partial mitigation only. Additionally, run the client process under a least-privileged account whose write permissions are confined to the intended download path, and harden the transport against the server/MITM prerequisite by enforcing TLS certificate validation and, where feasible, pinning or otherwise verifying the identity of the ticket server. Reference the vendor advisory at https://cert-portal.siemens.com/productcert/html/ssa-390352.html for the official fix guidance.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerable component is a client-side .NET library that speaks to the SIMATIC S7 Webserver API and, as part of its workflow, downloads tickets from a remote server and writes them to a local download directory. Although it performs the network-facing role in those transactions, it is not a listening service, which is why the attack surface is inverted relative to a typical path-traversal bug: the untrusted input is the ticket response produced by the remote server, not a request to a local daemon. The library fails to validate the filename supplied in that response (CWE-22, Improper Limitation of a Pathname to a Restricted Directory), so relative or absolute traversal sequences survive into the file-write call and land outside the intended directory. The CPE cpe:2.3:a:siemens:.net_client_library_for_simatic_s7_webserver_api:* confirms the whole version line below V3.3.61 is affected, and the vendor classifies the impact strictly as unauthorized modification of files (integrity), with no direct read or denial-of-service primitive.
Know when Net Client Library For Simatic S7 Webserver Api gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
Network-reachable via the server the client connects to with no added privilege or interaction (PR:N/UI:N); impact is arbitrary file write, so I:H with C:N/A:N and no scope change.
Primary rating from Vendor (siemens).
CVSS VectorVendor: siemens
Lifecycle Timeline
2DescriptionCVE.org
A vulnerability has been identified in .NET Client Library for SIMATIC S7 Webserver API (All versions < V3.3.61). Affected applications do not properly validate filenames received from remote servers during ticket downloads.
This could allow an attacker who can manipulate the ticket response to write arbitrary files outside the intended download directory and, when overwriting is enabled, replace existing files accessible to the application.
Executive ViewAI
The Siemens .NET Client Library for the SIMATIC S7 Webserver API (all versions prior to V3.3.61) is affected by a high-severity path traversal vulnerability that allows an unauthenticated attacker who controls or man-in-the-middle the server to write arbitrary files on client systems, potentially compromising the integrity of industrial control operations. With no vendor-released patch identified at time of analysis, affected organizations face a persistent risk of system compromise and operational disruption. Leadership should prioritize immediate network segmentation and monitoring to protect critical infrastructure until a patched version becomes available.
No vendor-released patch identified at time of analysis; interim mitigations include enforcing TLS for all ticket downloads, restricting outbound network connections to trusted servers, implementing network segmentation, limiting file system write permissions for the client application, enabling file integrity monitoring, and disabling file overwriting if not essential.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.
EUVD-2026-98392
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB