CVE-2021-22771
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-1236: Improper Neutralization of Formula Elements in a CSV File vulnerability exists in Easergy T300 with firmware V2.7.1 and older that would allow arbitrary command execution.
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-1236 Improper Neutralization of Formula Elements in a CSV File vulnerability in Schneider Electric's Easergy T300 firmware V2.7.1 and older allows arbitrary command execution through malicious formula injection in CSV files. This is a CSV injection leading to command execution in an industrial control device.
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.7.1CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify firmware version of Easergy T300 deviceAccess the device web interface or administrative console and navigate to the firmware version or system information section. Alternatively, check the device's about or status page for the installed firmware version number.Affected if The installed firmware version is 2.7.1 or older.
-
Confirm CSV import functionality is accessibleLocate any feature on the device or its web interface that allows importing or uploading CSV files, such as configuration backup/restore, data import, or report generation features.Affected if CSV import functionality exists and is enabled on the device.
-
Check device network exposureDetermine if the device web interface or administrative ports are exposed directly to untrusted networks or the internet. Review firewall rules and network segmentation around the device.Affected if The device administrative interface is reachable from untrusted networks without proper access controls.
-
Review CSV processing logs or audit trailsExamine device logs for any entries related to CSV file imports, formula execution, or suspicious command activity. Check system event logs for any indicators of formula injection attempts.Affected if Logs show recent CSV imports or any evidence of formula characters (such as =, +, -, @) being processed.
A user is affected if the Easergy T300 device runs firmware version 2.7.1 or older and has CSV import functionality enabled and accessible.
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 a version newer than V2.7.1 per Schneider Electric's recommended patch path, or implement input validation/sanitization for CSV file imports as a compensating control if immediate upgrade is not feasible.
- Consultation4.0 h
- Implementation3.0 h
- Testing6.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 $4,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22771 — 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-2021-22771 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