CVE-2021-22708
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-347: Improper Verification of Cryptographic Signature vulnerability exists in EVlink City (EVC1S22P4 / EVC1S7P4 all versions prior to R8 V3.4.0.1), EVlink Parking (EVW2 / EVF2 / EV.2 all versions prior to R8 V3.4.0.1), and EVlink Smart Wallbox (EVB1A all versions prior to R8 V3.4.0.1 ) that could allow an attacker to craft a malicious firmware package and bypass the signature verification mechanism.
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-347 improper cryptographic signature verification vulnerability in Schneider Electric EVlink charging stations allows attackers to craft and install malicious firmware by bypassing the signature validation mechanism. This affects the firmware update process for EVlink City, Parking, and Smart Wallbox products.
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< r8_v3.4.0.1< r8_v3.4.0.1< r8_v3.4.0.1< r8_v3.4.0.1< r8_v3.4.0.1< r8_v3.4.0.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
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the EVlink modelLocate the device model label on the charging station or access it through the device's admin/management interface. Look for model identifiers: Evc1s22p4, Evc1s7p4, Evw2, Evf2, Ev.2, or Evb1a.Affected if The model matches one of the affected products: EVlink City (Evc1s22p4, Evc1s7p4), EVlink Parking (Evw2, Evf2, Ev.2), or EVlink Smart Wallbox (Evb1a).
-
Retrieve the installed firmware versionAccess the charging station's firmware information through its web interface, mobile app, or diagnostic port. Navigate to the system information, device status, or firmware details section.Affected if The firmware version cannot be retrieved or the device is running firmware prior to r8_v3.4.0.1.
-
Compare firmware version against the affected rangeDocument the exact firmware version string displayed in the device information (for example: check if it shows r8_v3.x.x.x or earlier). Compare your version against r8_v3.4.0.1.Affected if The installed firmware version is lower than r8_v3.4.0.1 (for example: r8_v3.3.0.2, r8_v2.x.x.x, or any version not containing the 3.4.0.1 patch).
A user is affected if they are running any EVlink City, Parking, or Smart Wallbox charging station with firmware version earlier than r8_v3.4.0.1.
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 dataUpdate all affected EVlink devices to firmware version R8 V3.4.0.1 or later, which contains the patched signature verification mechanism. Prioritize devices with exposed firmware update interfaces.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22708 — 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-22708 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