dbcve.org
ComosApplication · Siemens

CVE-2021-37196

MEDIUM · 6.5 CVSS v3.1 Published 2022-01-11
Fix available
A fix is available. Upgrade to 10.3.3.3 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability has been identified in COMOS V10.2 (All versions only if web components are used), COMOS V10.3 (All versions < V10.3.3.3 only if web components are used), COMOS V10.3 (All versions >= V10.3.3.3 only if web components are used), COMOS V10.4 (All versions < V10.4.1 only if web components are used). The COMOS Web component of COMOS unpacks specially crafted archive files to relative paths. This vulnerability could allow an attacker to store files in any folder accessible by the COMOS Web webservice.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ComosApplication
Affected:<= 10.2>= 10.3, < 10.3.3.3= 10.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.3.3.3 or later
Fixed in 10.3.3.3
Vendor patch cert-portal.siemens.com →
Recommended fix Moderate confidence

V10.3.3.3 or later for V10.3 branch; V10.4.1 or later for V10.4 branch

  1. 1. Review the vendor patch document at https://cert-portal.siemens.com/productcert/pdf/ssa-995338.pdf for detailed remediation guidance
  2. 2. Identify the currently installed COMOS version by checking the application or system information
  3. 3. For COMOS V10.2: Upgrade to a version where the path traversal vulnerability in web components is resolved (contact Siemens for specific fixed version)
  4. 4. For COMOS V10.3: Upgrade to V10.3.3.3 or later as this version addresses the vulnerability
  5. 5. For COMOS V10.4: Upgrade to V10.4.1 or later as this version includes the security fix
  6. 6. After upgrading, verify the COMOS Web component functionality to ensure the fix does not introduce regressions
  7. 7. Test that the path traversal vulnerability is no longer exploitable by attempting to create files outside intended directories

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-37196 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-37196 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data