CVE-2021-22774
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-759: Use of a One-Way Hash without a Salt 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 lead an attacker to get knowledge of charging station user account credentials using dictionary attacks techniques.
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 confidenceThe vulnerability involves the use of unsalted one-way hash functions for storing user account passwords in EVlink charging station firmware. Without salt, identical passwords produce identical hashes, enabling precomputed rainbow tables or dictionary attacks to recover plaintext passwords from stolen hash values.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 device modelAccess the device management interface or check the physical device label to determine the exact model (Evc1s22p4, Evc1s7p4, Evw2, Evf2, Ev.2, or Evb1a)Affected if The device model is one of the listed affected products and the firmware version cannot be determined or is not visible for verification
-
Determine the firmware versionLog into the device admin panel or check the device status page to locate the firmware version information; compare against the version string r8_v3.4.0.1Affected if The installed firmware version is earlier than r8_v3.4.0.1 (for example, r8_v3.3.x.x or any version with a lower numeric sequence)
-
Check for user account configurationExamine the device user management or accounts settings to see if any user accounts have been created for accessing the charging stationAffected if User accounts exist on the device, as the vulnerability only affects environments with configured passwords that would be stored using the weak hashing method
-
Inspect password storage mechanism if accessibleIf you have administrative access to the underlying system, examine the configuration files or database where user credentials are stored; look for password hash valuesAffected if Password hashes are stored without a salt value (the hash appears as a simple MD5/SHA digest without random salt prefix or suffix)
You are affected if your EVlink device runs firmware versions earlier than r8_v3.4.0.1 and has user accounts configured for administrative or user access.
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 City, EVlink Parking, and EVlink Smart Wallbox deployments to firmware version R8 V3.4.0.1 or later, which implements salted password hashing.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22774 — 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-22774 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