CVE-2020-28395
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 SCALANCE X-200RNA switch family (All versions < V3.2.7), SCALANCE X-300 switch family (incl. X408 and SIPLUS NET variants) (All versions < V4.1.0). Devices do not create a new unique private key after factory reset. An attacker could leverage this situation to a man-in-the-middle situation and decrypt previously captured traffic.
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 confidenceThe SCALANCE X-200RNA and X-300 switch families retain the same private cryptographic key after a factory reset instead of generating a new unique key. This allows an attacker who previously captured encrypted traffic and can perform a man-in-the-middle attack to decrypt that traffic using the known private key.
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< 4.1.0< 4.1.0< 4.1.0< 4.1.0< 4.1.0< 4.1.0< 4.1.0< 4.1.0CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
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 SCALANCE device modelAccess the device web interface, CLI, or management console and locate the product name/model information. Common paths: System > Device Information in web UI, or 'show device' command in CLI.Affected if The model is one of: XR324 12m, XR324 12m Ts, XR324 4m Eec, XR324 4m Poe, XR324 4m Poe Ts, XR324wg, XR326 2c Poe Wg, or XR328 4c Wg.
-
Check the installed firmware versionIn the device web interface, go to System > Firmware or use the CLI command 'show firmware version'. Record the exact version string.Affected if The firmware version is below 4.1.0 (for example, 3.x.x or any version less than 4.1.0).
-
Determine if factory reset has been performedReview device administration logs or check with the network administrator to confirm whether a factory reset has ever been executed on the device.Affected if A factory reset has been performed on a device with firmware below 4.1.0, because the vulnerability allows the private key to remain unchanged after reset.
You are affected if your device is one of the listed SCALANCE X-200RNA or X-300 models and is running firmware version below 4.1.0 and has undergone a factory reset.
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 data4.1.0
Upgrade firmware to V3.2.7 or later for X-200RNA devices, and V4.1.0 or later for X-300 devices to ensure new unique keys are generated on factory reset.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-28395 — 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-28395 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