CVE-2020-28392 json
A vulnerability has been identified in SIMARIS configuration (All versions < V4.0.1).
published 5y ago modified 4mo ago also EUVD-2020-20851
- cvss
- 7.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 22%
- public exploits
- 0
- none known
Summary
A vulnerability has been identified in SIMARIS configuration (All versions < V4.0.1). During installation to default target folder, incorrect permissions are configured for the application folder and subfolders which could allow an attacker to gain persistence or potentially escalate privileges should a user with elevated credentials log onto the machine.
Patch / fix
Is CVE-2020-28392 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-21-040-08 updated cvss 4.4
Siemens SIMARIS Configuration (Update A)
-
Siemens SIMARIS configuration < 4.0.1affected: vendor fix support.industry.siemens.com
From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf
Exploit prediction
0.30% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 4.6 | AV:L/AC:L/Au:N/C:P/I:P/A:P |
Affected products
- Siemens SIMARIS configuration
Classification
- Weakness
-
- CWE-276 Incorrect Default Permissions
References
-
cert-portal.siemens.com
/productcert/pdf/ssa-794542.pdf
patch, vendor-advisory
Sources
- CVE List CVE-2020-28392
- NVD CVE-2020-28392
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.