CVE-2020-28218
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-1021: Improper Restriction of Rendered UI Layers or Frames vulnerability exists in Easergy T300 (firmware 2.7 and older), that would allow an attacker to trick a user into initiating an unintended action.
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 confidenceA clickjacking vulnerability (CWE-1021) in the Easergy T300 web interface allows attackers to embed the device's UI in an iframe and overlay invisible or disguised malicious UI elements, tricking authenticated users into performing unintended actions such as clicking configuration buttons they did not intend to.
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<= 2.7CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 Easergy T300 firmware versionAccess the device's web interface and navigate to the firmware/version information page, typically found in System Settings or About section. Alternatively, check the device's administrative console for firmware version display.Affected if The displayed firmware version is 2.7 or lower (any version <= 2.7).
-
Verify web interface is accessibleAttempt to access the Easergy T300 web interface via HTTP/HTTPS from a browser or curl command: curl -I http://<device-ip>/ or https://<device-ip>/Affected if The web interface responds and is reachable over the network.
-
Check for X-Frame-Options headerSend an HTTP request to the web interface and inspect the response headers for X-Frame-Options: curl -I -s http://<device-ip>/ | grep -i x-frame-optionsAffected if The X-Frame-Options header is missing, or the header value is not set to DENY or SAMEORIGIN.
-
Check Content Security Policy for frame-ancestorsInspect the HTTP response headers for Content-Security-Policy: curl -I -s http://<device-ip>/ | grep -i content-security-policyAffected if No Content-Security-Policy header exists, or the frame-ancestors directive is missing or does not restrict framing.
You are affected if the Easergy T300 firmware is version 2.7 or lower AND the web interface is accessible AND the X-Frame-Options header is missing/weak AND CSP frame-ancestors is not configured.
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 dataAdd X-Frame-Options: DENY or SAMEORIGIN HTTP response headers, or implement Content Security Policy with frame-ancestors directive to prevent the web interface from being framed by untrusted sources.
- Consultation3.0 h
- Implementation4.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 $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-28218 — 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-28218 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