CVE-2020-7507
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-400: Uncontrolled Resource Consumption vulnerability exists in Easergy T300 (Firmware version 1.5.2 and older) which could allow an attacker to login multiple times resulting in a denial of service.
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 confidenceA CWE-400 Uncontrolled Resource Consumption vulnerability in Schneider Electric's Easergy T300 (firmware 1.5.2 and older) allows attackers to repeatedly attempt login attempts without proper rate limiting or account lockout, exhausting server resources and causing denial of service to legitimate users.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the Easergy T300 web interface or use SNMP/management interface to confirm the device is an Easergy T300 unit. Check system information or device status page for the model name.Affected if The device is not an Easergy T300 unit.
-
Determine the installed firmware versionLog into the Easergy T300 management interface and navigate to System > Firmware or About section to view the current firmware version number.Affected if Firmware version is 1.5.2 or older.
-
Verify rate limiting on authentication endpointsInspect the web server or application configuration files for authentication-related settings. Look for rate-limit, throttle, or request-limiting configurations on login/form authentication endpoints. Use web proxy to observe response headers when making repeated login POST requests.Affected if No rate limiting configuration exists or rate limiting is disabled on authentication endpoints.
-
Check for account lockout policy configurationReview user management or security policy settings in the web interface under User Management, Security Settings, or Account Policy. Verify if account lockout after failed attempts is enabled and note the threshold.Affected if Account lockout is disabled or not configured, allowing unlimited failed login attempts.
-
Inspect for resource exhaustion indicatorsReview system logs, authentication logs, or audit logs for patterns of repeated login attempts from single sources. Check system resource usage (CPU, memory, connection limits) during normal operation versus periods of failed login activity.Affected if Logs show high volumes of authentication attempts without blocks, or system resources become depleted during login storms.
The environment is affected if the device is an Easergy T300 running firmware version 1.5.2 or older, and authentication endpoints lack rate limiting or account lockout controls.
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 dataImplement account lockout policies and rate limiting on authentication endpoints, and upgrade to firmware version newer than 1.5.2 if a patch is available.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7507 — 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-7507 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