Container data corruption via writable root filesystem
Published Aug 13, 2024 · Updated Aug 13, 2024
Improper privilege management in Siemens SINEC Traffic Analyzer before 2.0 allows remote authenticated users to corrupt container data. The deployment configuration mounts the container root filesystem read-write instead of enforcing a read-only boundary. High-privilege access to the network service is required, after which attackers can modify or corrupt data inside the container.
Summary
What happened
Improper privilege management in Siemens SINEC Traffic Analyzer before 2.0 allows remote authenticated users to corrupt container data. The deployment configuration mounts the container root filesystem read-write instead of enforcing a read-only boundary. High-privilege access to the network service is required, after which attackers can modify or corrupt data inside the container.
The record
- CVE
- CVE-2024-41903
- Published
- Aug 13, 2024
- Updated
- Aug 13, 2024
- Vendor
- Siemens
- Product
- SINEC Traffic Analyzer
- Classifications
- CWE-269, T1565.001
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Aug 13, 2024CVE publishedPublication date reported by the CVE source.
- Aug 13, 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 <2.0
- Affected versionversion=0 <V2.0
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.
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