CVE-2021-35957
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 · uneditedStormshield Endpoint Security Evolution 2.0.0 through 2.0.2 does not accomplish the intended defense against local administrators who can replace the Visual C++ runtime DLLs (in %WINDIR%\system32) with malicious ones.
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 confidenceStormshield Endpoint Security Evolution versions 2.0.0 through 2.0.2 fails to prevent local administrators from replacing Visual C++ runtime DLLs in %WINDIR%\system32 with malicious versions, allowing DLL hijacking and potential privilege escalation or code execution in the context of other processes loading those DLLs.
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.0.0, <= 2.0.2CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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.
-
Verify Stormshield Endpoint Security Evolution versionCheck the installed version of Stormshield Endpoint Security Evolution using the product's built-in version information (typically available in the product GUI under About/Help, or via registry key if documented by vendor)Affected if The installed version is 2.0.0, 2.0.1, or 2.0.2 (any version from 2.0.0 through 2.0.2 inclusive)
-
Confirm Visual C++ runtime DLLs exist in system32Enumerate the Visual C++ runtime DLL files (such as msvcr*.dll, msvcp*.dll, or similar) present in %WINDIR%\system32Affected if Any VC++ runtime DLLs are present in system32 and the product version is in the affected range
-
Check file permissions on system32 DLLsReview ACLs (Access Control Lists) on the VC++ runtime DLLs in system32 to determine if standard users or administrators have write permissionsAffected if Write permissions are granted to non-privileged users on VC++ runtime DLLs in system32 (enabling the DLL replacement vector)
-
Inspect for unauthorized DLL modificationsUse file integrity monitoring tools or compare current DLL hashes in system32 against known-good baselines for VC++ runtime filesAffected if Any VC++ runtime DLLs in system32 have been modified from their expected hashes or baselines
A user is affected if Stormshield Endpoint Security Evolution version 2.0.0 through 2.0.2 is installed and Visual C++ runtime DLLs in system32 are present and potentially modifiable.
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 dataApply vendor patch when available; in the interim, restrict administrative privileges where feasible, monitor system32 for unauthorized DLL modifications, and implement additional endpoint detection controls.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-35957 — 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-35957 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