dbcve.org
Sicam Mmu FirmwareOperating system · Siemens

CVE-2020-10038

CRITICAL · 9.8 CVSS v3.1 Published 2020-07-14
Fix available
A fix is available. Upgrade to 2.05 / 2.18 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 SICAM MMU (All versions < V2.05), SICAM SGU (All versions), SICAM T (All versions < V2.18). An attacker with access to the device's web server might be able to execute administrative commands without authentication.

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 · moderate confidence

Authentication bypass in Siemens SICAM web servers (MMU, SGU, T series) allows unauthenticated attackers to execute administrative commands by directly accessing web API endpoints without valid credentials. This is a pre-authentication privilege escalation flaw in the web interface component.

MitigationApply vendor patches (V2.05 for SICAM MMU, V2.18 for SICAM T). For SICAM SGU (no patch available) and unpatched instances, implement network segmentation to restrict access to the web server and disable it if not required.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Sicam Mmu FirmwareOperating system
Affected:< 2.05
Sicam Sgu FirmwareOperating system
Affected:all versions
Sicam T FirmwareOperating system
Affected:< 2.18

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify SICAM devices in your environment
    Inventory all Siemens SICAM devices, specifically looking for MMU, SGU, or T series units. Check your asset inventory or perform network discovery for devices with SICAM firmware.
    Affected if No SICAM devices present means not affected at this step.
  2. Determine the exact model variant
    Identify whether the SICAM device is an MMU, SGU, or T series unit. Check the device label, management interface, or asset documentation for the model designation.
    Affected if If the model is not MMU, SGU, or T, the specific CVE does not apply.
  3. Check installed firmware version
    Access the device management interface or use the vendor-specific command to retrieve the firmware version. Compare the installed version against: MMU < 2.05, SGU all versions, T < 2.18.
    Affected if The device is potentially affected if the firmware version falls within the affected ranges: MMU with version < 2.05, SGU any version, T with version < 2.18.
  4. Verify web interface component is enabled
    Check the device configuration or web server settings to determine if the SICAM web interface (HTTP/HTTPS service) is currently enabled.
    Affected if The vulnerability only applies if the web interface component is enabled; if it is disabled, the attack surface does not exist.
  5. Assess network accessibility of the web service
    Determine if the web interface is exposed to network segments accessible to untrusted users. Check firewall rules, ACLs, and network zone placements.
    Affected if If the web interface is reachable from untrusted networks without adequate segmentation, the device is at higher risk of exploitation.

Your environment is affected if you have a SICAM MMU (firmware < 2.05), SICAM SGU (any version), or SICAM T (firmware < 2.18) with the web interface enabled and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 2.05 / 2.18 or later
Fixed in 2.052.18
Interim mitigation

Apply vendor patches (V2.05 for SICAM MMU, V2.18 for SICAM T). For SICAM SGU (no patch available) and unpatched instances, implement network segmentation to restrict access to the web server and disable it if not required.

Recommended fix High confidence

Sicam Mmu: V2.05 or later; Sicam T: V2.18 or later; Sicam SGU: Contact vendor for fixed release

  1. 1. Identify the specific Sicam device model (MMU, SGU, or T) in your environment
  2. 2. Determine the current firmware version installed on the device
  3. 3. For Sicam MMU: Upgrade to firmware version 2.05 or later from Siemens support channels
  4. 4. For Sicam T: Upgrade to firmware version 2.18 or later from Siemens support channels
  5. 5. For Sicam SGU: Contact Siemens Product Security for available fixes, as all versions are affected
  6. 6. After upgrading, verify the web server requires authentication for administrative functions
  7. 7. Restrict network access to the device's web server to trusted networks only as an additional mitigation
Caveat Review Siemens release notes for any configuration or compatibility changes in new firmware versions

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

Fix this in Sicam Mmu Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-10038 — 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-2020-10038 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