CVE-2020-28391: A vulnerability has been identified in SCALANCE X-200 switch family (incl.
Noroxi assessment
Priority: Monitor (action score 23/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.1% (FIRST EPSS); higher than 66.6% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A vulnerability has been identified in SCALANCE X-200 switch family (incl. SIPLUS NET variants) (All versions < V5.2.5), SCALANCE X-200IRT switch family (incl. SIPLUS NET variants) (All versions < V5.5.0), SCALANCE X-200RNA switch family (All versions < V3.2.7). Devices create a new unique key upon factory reset, except when used with C-PLUG. When used with C-PLUG the devices use the hardcoded private RSA-key shipped with the firmware-image. An attacker could leverage this situation to a man-in-the-middle situation and decrypt previously captured traffic.
- Published
- Jan 12, 2021
- Updated
- Jun 16, 2026
- EPSS
- 1.1% · 66th percentile
- CWE
- CWE-321
Report tools
Action score
23
Monitor
Low priority for now.
- CVSS
- 23 / 40 · 5.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| siemens | scalance x200-4pirt firmware | cpe:2.3:o:siemens:scalance_x200-4pirt_firmware |
| siemens | scalance x200-4pirt | cpe:2.3:h:siemens:scalance_x200-4pirt |
| siemens | scalance x201-3pirt firmware | cpe:2.3:o:siemens:scalance_x201-3pirt_firmware |
| siemens | scalance x201-3pirt | cpe:2.3:h:siemens:scalance_x201-3pirt |
| siemens | scalance x202-2irt firmware | cpe:2.3:o:siemens:scalance_x202-2irt_firmware |
| siemens | scalance x202-2irt | cpe:2.3:h:siemens:scalance_x202-2irt |
| siemens | scalance x202-2pirt firmware | cpe:2.3:o:siemens:scalance_x202-2pirt_firmware |
| siemens | scalance x202-2pirt | cpe:2.3:h:siemens:scalance_x202-2pirt |
| siemens | scalance x202-2pirt siplus net firmware | cpe:2.3:o:siemens:scalance_x202-2pirt_siplus_net_firmware |
| siemens | scalance x202-2pirt siplus net | cpe:2.3:h:siemens:scalance_x202-2pirt_siplus_net |
| siemens | scalance x204irt firmware | cpe:2.3:o:siemens:scalance_x204irt_firmware |
| siemens | scalance x204irt | cpe:2.3:h:siemens:scalance_x204irt |
and 120 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- siemens scalance x200-4pirt firmwarebefore 5.5.0
- siemens scalance x201-3pirt firmwarebefore 5.5.0
- siemens scalance x202-2irt firmwarebefore 5.5.0
- siemens scalance x202-2pirt firmwarebefore 5.5.0
- siemens scalance x202-2pirt siplus net firmwarebefore 5.5.0
- siemens scalance x204irt firmwarebefore 5.5.0
- siemens scalance x307-3 firmwareall versions
- siemens scalance x307-3ld firmwareall versions
- siemens scalance x308-2 firmwareall versions
- siemens scalance x308-2ld firmwareall versions
- siemens scalance x308-2lh firmwareall versions
- siemens scalance x308-2lh+ firmwareall versions
- siemens scalance x308-2m firmwareall versions
- siemens scalance x308-2m ts firmwareall versions
- siemens scalance x310 firmwareall versions
- siemens scalance x310fe firmwareall versions
- siemens scalance x320-1fe firmwareall versions
- siemens scalance x320-3ldfe firmwareall versions
- siemens scalance xb205-3 firmwarebefore 5.2.5
- siemens scalance xb205-3ld firmwarebefore 5.2.5
Versions reported by the vendor
Affected version ranges reported by the assigning authority (siemens). Independent of NVD's CPE analysis and usually ahead of it.
Siemens SCALANCE X-200 switch family (incl. SIPLUS NET variants)
- All versions < V5.2.5affected
Siemens SCALANCE X-200IRT switch family (incl. SIPLUS NET variants)
- All versions < V5.5.0affected
Siemens SCALANCE X-200RNA switch family
- All versions < V3.2.7affected
Same product
siemens: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-25226A vulnerability has been identified in SCALANCE X-200 switch family (incl.40Plan
- CVE-2020-15800A vulnerability has been identified in SCALANCE X-200 switch family (incl.40Plan
- CVE-2020-15799A vulnerability has been identified in SCALANCE X-200 switch family (incl.26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-321 · Use of Hard-coded Cryptographic KeyCVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.