CVE-2020-7513
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 CWE-312: Cleartext Storage of Sensitive Information vulnerability exists in Easergy T300 (Firmware version 1.5.2 and older) which could allow an attacker to intercept traffic and read configuration data.
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 Easergy T300 firmware version 1.5.2 and older stores sensitive configuration data in cleartext, allowing network attackers to intercept traffic and read this data. This CWE-312 vulnerability exposes sensitive information during transmission without encryption protection.
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<= 1.5.2CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/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.
-
Confirm Easergy T300 device presenceIdentify if Schneider Electric Easergy T300 is deployed in your environment by checking device inventory, network documentation, or physically inspecting device labelsAffected if Easergy T300 device is present in the environment
-
Check installed firmware versionAccess the device web interface or use the manufacturer's management software to view the firmware version information, typically found in System Info or About sectionsAffected if Firmware version is 1.5.2 or lower
-
Inspect network traffic for cleartext dataCapture network packets traveling to/from the Easergy T300 device using a packet sniffer (such as Wireshark) and examine if sensitive configuration data (credentials, settings, system parameters) is transmitted without encryptionAffected if Sensitive configuration data is visible in cleartext within captured network packets
-
Verify encryption protection on configuration accessCheck if the device web interface or management protocols (HTTP, FTP, Telnet) are using SSL/TLS encryption by examining connection details and protocol headersAffected if Device management or configuration interfaces are accessible over unencrypted protocols (HTTP, FTP, Telnet)
You are affected if you have an Easergy T300 device running firmware version 1.5.2 or lower, and sensitive configuration data is transmitted over the network without encryption protection.
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 dataUpgrade Easergy T300 firmware to version 1.5.3 or later. Until then, isolate the device on a secured network segment and monitor for unauthorized traffic interception attempts.
- Consultation6.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7513 — 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-7513 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