Forged requests via flawed CSRF prevention
Published Jan 11, 2022 · Updated May 22, 2025
Cross-site request forgery in Siemens COMOS Web 10.2, 10.3 before 10.3.3.3, and 10.4 before 10.4.1 allows remote attackers to submit forged requests. Siemens has not disclosed the affected endpoint or the validation operation that the CSRF control performs incorrectly. Exploitation requires user interaction and a deployment using COMOS Web; the forged request can act with the user's session, but the resulting action is undisclosed.
Summary
What happened
Cross-site request forgery in Siemens COMOS Web 10.2, 10.3 before 10.3.3.3, and 10.4 before 10.4.1 allows remote attackers to submit forged requests. Siemens has not disclosed the affected endpoint or the validation operation that the CSRF control performs incorrectly. Exploitation requires user interaction and a deployment using COMOS Web; the forged request can act with the user's session, but the resulting action is undisclosed.
The record
- CVE
- CVE-2021-37198
- Published
- Jan 11, 2022
- Updated
- May 22, 2025
- Vendor
- Siemens
- Product
- COMOS
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 11, 2022CVE publishedPublication date reported by the CVE source.
- May 22, 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.
- Affected versionversion=All versions only if web components are used
- Affected versionversion=All versions < V10.3.3.3 only if web components are used
- Affected versionversion=All versions < V10.4.1 only if web components are used
What conditions does exploitation require?
What is affected?
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