Update disruption via insecure temporary-file directory
Published Jun 11, 2024 · Updated Aug 2, 2024
Insecure temporary-file creation in Siemens TIA Administrator before V3 SP2 allows local users to disrupt software updates. The download component writes temporary files beneath the installation path into a directory whose permissions allow non-administrative users to alter them. Exploitation requires an authenticated Windows account; the documented consequence is interruption of the update process.
Summary
What happened
Insecure temporary-file creation in Siemens TIA Administrator before V3 SP2 allows local users to disrupt software updates. The download component writes temporary files beneath the installation path into a directory whose permissions allow non-administrative users to alter them. Exploitation requires an authenticated Windows account; the documented consequence is interruption of the update process.
The record
- CVE
- CVE-2023-38533
- Published
- Jun 11, 2024
- Updated
- Aug 2, 2024
- Vendor
- Siemens
- Product
- TIA Administrator
- Classifications
- CWE-379
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 11, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record 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.
- Affected versionversion=0 <v3sp2
- Affected versionversion=0 <V3 SP2
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
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