dbcve.org
Easergy T300 FirmwareOperating system · Schneider Electric

CVE-2020-28215

CRITICAL · 9.8 CVSS v3.1 Published 2020-12-11
Fix available
A fix is available. Upgrade to after 2.7 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
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.

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 · moderate confidence

A CWE-862 Missing Authorization vulnerability in Schneider Electric Easergy T300 firmware 2.7 and older allows attackers to bypass inconsistent access control checks, potentially enabling information exposure, denial of service, or arbitrary code execution on this industrial power management device.

MitigationIf available, upgrade Easergy T300 to firmware newer than 2.7; otherwise implement network segmentation, firewall rules, and compensating controls to restrict access to the T300 management interfaces to authorized personnel only.

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
Easergy T300 FirmwareOperating system
Affected:<= 2.7

CVSS 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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm device model is Schneider Electric Easergy T300
    Identify the device on your network or physically inspect the hardware label to verify the model number is Easergy T300
    Affected if The device is not an Easergy T300 unit
  2. Determine installed firmware version
    Access the device management interface or check the firmware version displayed in the device status/maintenance section; compare your version to the affected range <= 2.7
    Affected if Firmware version is 2.7 or older
  3. Verify management interface accessibility
    Test network access to the device web interface, API endpoints, or remote management ports from untrusted network segments
    Affected if Management interfaces are reachable from networks outside the trusted administrative zone without authentication barriers
  4. Review access control configuration
    Inspect the device security settings, user accounts, and authorization policies to determine if inconsistent or missing authorization checks exist on certain functions
    Affected if Any management functions are accessible without enforced authentication or authorization controls

You are likely affected if the device is an Easergy T300 running firmware version 2.7 or older and its management interfaces are accessible without proper authorization controls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2.7
Interim mitigation

If available, upgrade Easergy T300 to firmware newer than 2.7; otherwise implement network segmentation, firewall rules, and compensating controls to restrict access to the T300 management interfaces to authorized personnel only.

Recommended fix Moderate confidence

Firmware version higher than 2.7 (contact Schneider Electric for exact fixed release)

  1. 1. Identify the current firmware version of the Easergy T300 device by accessing the device management interface or checking system documentation.
  2. 2. Contact Schneider Electric technical support or visit the official SE.com support portal to obtain the firmware update that addresses CVE-2020-28215.
  3. 3. Review all release notes and security bulletins associated with the firmware update to understand changes and any special upgrade instructions.
  4. 4. Create a full backup of the current device configuration before initiating the firmware upgrade.
  5. 5. Follow the official Schneider Electric firmware upgrade procedure for the Easergy T300, ensuring stable power supply during the process.
  6. 6. After upgrade completion, verify the new firmware version and confirm that authorization controls are functioning correctly.
  7. 7. Test that access control checks are now consistently applied across all device functions mentioned in the vulnerability (information exposure, DoS, code execution vectors).
Caveat Review Schneider Electric release notes for any configuration or compatibility changes in the newer firmware version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Easergy T300 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-28215 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-28215 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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