CVE-2021-31814
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 · uneditedIn Stormshield 1.1.0, and 2.1.0 through 2.9.0, an attacker can block a client from accessing the VPN and can obtain sensitive information through the SN VPN SSL Client.
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 · low confidenceA vulnerability in Stormshield SN VPN SSL Client (versions 1.1.0 and 2.1.0-2.9.0) allows remote attackers to both deny VPN access to legitimate clients and exfiltrate sensitive information. The specific technical weakness (injection, logic flaw, or authentication bypass) is not detailed in available sources.
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.1.0, <= 2.9.0= 1.1.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/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 installed Stormshield VPN SSL Client versionLocate and inspect the installed Stormshield SN VPN SSL Client version through the application's about dialog, installed programs list, or by running the client software and checking its version information. If using command-line tools, query the installed package or application metadata.Affected if The installed version is 1.1.0 or falls within the range 2.1.0 to 2.9.0 inclusive.
-
Confirm VPN SSL Client feature is active or configuredVerify whether the Stormshield VPN SSL Client feature is enabled, configured, or actively in use on the system. Check the client's connection status or configuration profile settings.Affected if The VPN SSL Client feature is enabled or configured on the system, making it a potential target for exploitation.
-
Review VPN access logs for anomalous connection patternsExamine Stormshield VPN server and client logs for unusual connection behaviors such as repeated failed connection attempts, unexpected disconnections, or irregular traffic patterns that could indicate denial of service or information exfiltration attempts.Affected if Logs reveal abnormal connection patterns, frequent access denials, or suspicious outbound traffic originating from the VPN client that deviate from normal operation.
A system is affected if it runs Stormshield SN VPN SSL Client version 1.1.0 or any version between 2.1.0 and 2.9.0 with the VPN client feature enabled.
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 Stormshield VPN clients and servers to versions beyond 2.9.0 where the vulnerability has been patched. If immediate patching is not feasible, monitor VPN access logs for anomalous connection patterns indicative of exploitation.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-31814 — 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-31814 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