CVE-2021-22728
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-200: Information Exposure 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 cause disclosure of encrypted credentials when consulting the maintenance report.
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 CWE-200 Information Exposure vulnerability in Schneider Electric EVlink charging stations (City, Parking, and Smart Wallbox) allows disclosure of encrypted credentials when a user accesses the maintenance report feature. The vulnerability exists in all versions prior to R8 V3.4.0.1.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify the EVlink charging station modelLocate the model number label on the charging station physical unit or in the device management interface. Confirm it matches one of these affected models: Evc1s22p4, Evc1s7p4, Evw2, Evf2, Ev.2, or Evb1a.Affected if The model number is one of the listed affected models.
-
Check the installed firmware versionAccess the charging station admin interface or use the manufacturer's diagnostic tool to retrieve the current firmware version. Look for a version string such as r8_v3.x.x.x or similar.Affected if The firmware version is anything earlier than r8_v3.4.0.1 (for example, r8_v3.3.0.0 or any version starting with r8_v3.x where x is less than 4).
-
Verify access to the maintenance report featureLog into the charging station management interface and navigate to the maintenance or diagnostics section to determine if a maintenance report feature exists and is accessible.Affected if The maintenance report feature is present and accessible to users, since this is the specific feature where encrypted credentials are disclosed.
The environment is affected if the charging station is one of the listed models, runs firmware prior to r8_v3.4.0.1, and has an accessible maintenance report feature that could expose encrypted credentials.
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 EVlink City, EVlink Parking, and EVlink Smart Wallbox firmware to R8 V3.4.0.1 or later to remediate the credential exposure in maintenance reports.
- 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-22728 — 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-22728 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