CVE-2020-28215
No exploitation reported by the sources we read.
- Published2020-12-11
- WeaknessCWE-862
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
A CWE-862: Missing Authorization vulnerability exists in Easergy T300 (firmware 2.7 and older), that could cause a wide range of problems, including information exposures, denial of service, and arbitrary code execution when access control checks are not applied consistently.
Timeline
dates in UTC- 2020-12-1101:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2020-28215?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2020-28215?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2.7 | ≤ 2.7 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Vendor advisories
Schneider Electric Easergy T300
Easergy T300 with firmware: Versions 2.7 and prior
Fix
- Mitigation from the vendor CISA ICSA-20-343-03 · 1 productSchneider Electric recommends users upgrade to v2.7.1, which is available from the Schneider Electric Customer Care Center. Alternatively, users may disable port forwarding in the product firewall.
- Mitigation from the vendor CISA ICSA-20-343-03 · 1 productLocate control and safety system networks and remote devices behind firewalls and isolate them from the business network.
- Mitigation from the vendor CISA ICSA-20-343-03 · 1 productInstall physical controls so no unauthorized personnel can access industrial control and safety systems, components, peripheral equipment, and networks.
- Mitigation from the vendor CISA ICSA-20-343-03 · 1 productPlace all controllers in locked cabinets and never leave them in “Program” mode.
- Mitigation from the vendor CISA ICSA-20-343-03 · 1 productNever connect programming software to any network other than the network for which the devices are intended.
- Mitigation from the vendor CISA ICSA-20-343-03 · 1 productScan all methods of mobile data exchange with the isolated network (e.g., CDs, USB drives, etc.) before use in the terminals or any node connected to these networks.
Advisories and patches
- www.se.comVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.19.8read 2026-10-23
- NVDCVSS 2.07.5read 2026-10-23
- CNAweakness (CWE)CWE-862read 2026-10-23
- FIRST EPSSEPSS score2.3 %2026-10-22
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2020-12-11
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2020-28215?
Is CVE-2020-28215 actively exploited?
What is the CVSS score for CVE-2020-28215?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.