CVE-2020-10044 json
A vulnerability has been identified in SICAM MMU (All versions < V2.05), SICAM SGU (All versions), SICAM T (All versions < V2.18).
published 6y ago modified 4mo ago also EUVD-2020-2509
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 57%
- public exploits
- 0
- none known
Summary
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 network could be able to install specially crafted firmware to the device.
Patch / fix
- siemens sicam_mmu_firmware 2.05
- siemens sicam_t_firmware 2.18
Is CVE-2020-10044 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-20-196-03 updated cvss 9.8
Siemens SICAM MMU, SICAM T, and SICAM SGU
-
Siemens SICAM MMU <V2.05affected: fixed in V2.05, mitigation
-
Siemens SICAM SGUaffected: mitigation
-
Siemens SICAM T <V2.18affected: fixed in V2.18, mitigation
Facts from CISA's republication of the vendor's own advisory (CSAF); the linked advisory is the authoritative source. CISA notification · csaf
Exploit prediction
0.83% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
Affected products
- Siemens AG SICAM MMU
- Siemens AG SICAM SGU
- Siemens AG SICAM T
Classification
- Weakness
-
- CWE-306 Missing Authentication for Critical Functionality
References
-
cert-portal.siemens.com
/productcert/pdf/ssa-305120.pdf
vendor-advisory
Sources
- CVE List CVE-2020-10044
- NVD CVE-2020-10044
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.