dbcve.org
Sicam Mmu FirmwareOperating system · Siemens

CVE-2020-10042

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). A buffer overflow in various positions of the web application might enable an attacker with access to the web application to execute arbitrary code over the network.

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

A buffer overflow vulnerability exists in the web interfaces of SICAM MMU (versions prior to V2.05), SICAM SGU (all versions), and SICAM T (versions prior to V2.18). The vulnerability is present in multiple locations within the web application and can be exploited by an attacker with web application access to achieve remote code execution over the network.

MitigationUpgrade SICAM MMU to V2.05 or later, SICAM SGU to the latest available version, and SICAM T to V2.18 or later. If immediate patching is not possible, restrict network access to the web application interface and monitor for exploitation attempts.

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 the installed SICAM product
    Locate the product name through the system inventory, device documentation, or web interface login page banner
    Affected if The product is SICAM MMU, SICAM SGU, or SICAM T
  2. Determine the firmware version
    Access the web interface admin panel or check the system information page for the firmware version number
    Affected if The version is less than V2.05 for SICAM MMU, any version for SICAM SGU, or less than V2.18 for SICAM T
  3. Verify the web interface is accessible
    Confirm the web application interface is enabled and reachable on the network by attempting to access the HTTP/HTTPS endpoints
    Affected if The web interface is exposed and the product/version check above indicates a vulnerable version
  4. Check for signs of exploitation
    Review web server logs for anomalous requests, unexpected processes, or indicators of compromise such as unusual POST parameters or buffer overflow patterns in access logs
    Affected if Suspicious patterns matching buffer overflow exploitation attempts are found in the logs

The environment is affected if a SICAM MMU version below V2.05, any SICAM SGU version, or SICAM T version below V2.18 is installed with the web interface 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

Upgrade SICAM MMU to V2.05 or later, SICAM SGU to the latest available version, and SICAM T to V2.18 or later. If immediate patching is not possible, restrict network access to the web application interface and monitor for exploitation attempts.

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. Check the current firmware version of the affected device through the web interface or device management system
  3. 3. For Sicam MMU: Download firmware version 2.05 or later from Siemens cert-portal.siemens.com
  4. 4. For Sicam T: Download firmware version 2.18 or later from Siemens cert-portal.siemens.com
  5. 5. For Sicam SGU: Contact Siemens directly for available fixes as all versions are affected
  6. 6. Before upgrading, review Siemens firmware upgrade documentation and ensure proper backup of device configuration
  7. 7. Upload and install the new firmware following Siemens official upgrade procedures
  8. 8. Verify the firmware installation was successful and the web application is functioning properly
Caveat Review Siemens release notes for any functional changes between current and new firmware version before upgrading

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

Fix this in Sicam Mmu Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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