CVE-2020-10045
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 · uneditedA vulnerability has been identified in SICAM MMU (All versions < V2.05), SICAM SGU (All versions), SICAM T (All versions < V2.18). An error in the challenge-response procedure could allow an attacker to replay authentication traffic and gain access to protected areas of the web application.
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 confidenceThis is a replay attack vulnerability in the challenge-response authentication mechanism of SICAM web applications. An attacker can capture valid authentication traffic and replay it to gain unauthorized access to protected areas of the web application, bypassing the intended authentication controls.
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< 2.05all versions< 2.18CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the SICAM product typeAccess the device management interface or check system documentation to determine whether the installed product is SICAM MMU, SICAM SGU, or SICAM T. This is typically visible in the device web interface or system information page.Affected if The product is any SICAM MMU, SGU, or T device with web authentication enabled
-
Determine the firmware version of SICAM MMUNavigate to the device web interface, typically at the IP address of the MMU unit. Look for a System Info, About, or Firmware version section in the administrative panel. Alternatively, check the device startup logs or use the vendor's management software to query the firmware version.Affected if The installed version is any version below V2.05 (for example, V2.04, V2.03, V1.x)
-
Determine the firmware version of SICAM TNavigate to the device web interface of the SICAM T unit. Look for a System Info, About, or Firmware version section in the administrative panel. Alternatively, check the device startup logs or use the vendor's management software to query the firmware version.Affected if The installed version is any version below V2.18 (for example, V2.17, V2.10, V1.x)
-
Check if SICAM SGU is installedIdentify if any SICAM SGU (Station Gateway Unit) device is present in the environment. This is typically found in substation automation deployments. Check device inventory or network documentation for SGU devices.Affected if Any SICAM SGU version is installed, as all versions are affected according to the vendor advisory
You are affected if you have any SICAM MMU with firmware below V2.05, any SICAM SGU of any version, or any SICAM T with firmware below V2.18, and the web-based authentication interface is enabled and accessible on the network.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data2.052.18
Upgrade SICAM MMU to version V2.05 or later and SICAM T to version V2.18 or later. For SICAM SGU, contact the vendor for patch availability since all versions are affected. Implement anti-replay controls such as nonces, timestamps, or sequence numbers in the authentication mechanism.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10045 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-10045 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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