Evlink City Evc1s22p4 FirmwareOperating system · Schneider Electric

CVE-2021-22773

MEDIUM · 6.5 CVSS v3.1 Published 2021-07-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A CWE-620: Unverified Password Change 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 connected to the charging station web server to modify the password of a user.

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 confidence

An Unverified Password Change vulnerability (CWE-620) in the web server of EVlink City, EVlink Parking, and EVlink Smart Wallbox charging stations allows an authenticated or network-adjacent attacker to modify user passwords without proper verification, potentially gaining unauthorized access to the charging station management interface.

MitigationUpdate affected charging station firmware to R8 V3.4.0.1 or later to obtain the vendor patch. Until then, restrict network access to the charging station web interfaces and monitor for unauthorized password change attempts.

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
Evlink City Evc1s22p4 FirmwareOperating system
Affected:< r8_v3.4.0.1
Evlink City Evc1s7p4 FirmwareOperating system
Affected:< r8_v3.4.0.1
Evlink Parking Evw2 FirmwareOperating system
Affected:< r8_v3.4.0.1
Evlink Parking Evf2 FirmwareOperating system
Affected:< r8_v3.4.0.1
Evlink Parking Ev.2 FirmwareOperating system
Affected:< r8_v3.4.0.1
Evlink Smart Wallbox Evb1a FirmwareOperating system
Affected:< r8_v3.4.0.1

CVSS 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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the EVlink model
    Locate the charging station model number on the physical device or in the management interface - look for Evc1s22p4, Evc1s7p4, Evw2, Evf2, Ev.2, or Evb1a designations
    Affected if The model matches one of the affected products: Evlink City Evc1s22p4, Evlink City Evc1s7p4, Evlink Parking Evw2, Evlink Parking Evf2, Evlink Parking Ev.2, or Evlink Smart Wallbox Evb1a
  2. Check the installed firmware version
    Access the charging station web interface or administrative panel and locate the firmware version information, typically found in Settings, About, or System Information sections
    Affected if The firmware version is earlier than r8_v3.4.0.1 (for example, r8_v3.3.x or any version with a lower build number)
  3. Determine if the web server is accessible
    Attempt to access the charging station web interface over the network using HTTP/HTTPS to confirm the web server is reachable
    Affected if The web interface is exposed and accessible from the network (authenticated or network-adjacent attackers require this access to exploit the vulnerability)
  4. Review access logs for password change operations
    Check the charging station or associated management system logs for any password modification requests, focusing on operations that lack proper verification patterns
    Affected if Logs show password changes that were initiated without proper user verification or that originated from unexpected sources

You are affected if you own any of the listed EVlink models and your firmware version is earlier than r8_v3.4.0.1, with the web interface accessible to authenticated or network-adjacent attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update affected charging station firmware to R8 V3.4.0.1 or later to obtain the vendor patch. Until then, restrict network access to the charging station web interfaces and monitor for unauthorized password change attempts.

Fix this in Evlink City Evc1s22p4 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-22773 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-22773 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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