CVE-2022-23989
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 Network Security (SNS) before 3.7.25, 3.8.x through 3.11.x before 3.11.13, 4.x before 4.2.10, and 4.3.x before 4.3.5, a flood of connections to the SSLVPN service might lead to saturation of the loopback interface. This could result in the blocking of almost all network traffic, making the firewall unreachable. An attacker could exploit this via forged and properly timed traffic to cause a denial of service.
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 confidenceA vulnerability in Stormshield SNS SSLVPN allows remote attackers to cause denial of service by flooding connections to the SSLVPN service. The flood of connections saturates the loopback interface, blocking almost all network traffic and making the firewall unreachable.
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>= 3.0.0, < 3.7.25>= 3.8.0, < 3.11.13>= 4.0.0, < 4.2.10>= 4.3.0, < 4.3.5CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Determine Stormshield SNS versionAccess the Stormshield CLI and run the command to display the firmware version (typically 'version' or check the web admin interface under System > Maintenance or Dashboard)Affected if The installed version falls within any of these ranges: >= 3.0.0 and < 3.7.25; >= 3.8.0 and < 3.11.13; >= 4.0.0 and < 4.2.10; or >= 4.3.0 and < 4.3.5
-
Confirm SSLVPN is enabledIn the Stormshield web admin interface, navigate to VPN > SSL VPN or SSLVPN configuration panel, or use CLI command 'sslvpn status' to check if the SSLVPN service is activeAffected if The SSLVPN module is actively enabled and the version is in an affected range from step 1
-
Check SSLVPN listen interfaceIn the SSL VPN configuration, examine the interface binding settings to see which IP addresses or interfaces the SSLVPN service is listening on (typically the external/WAN interface)Affected if SSLVPN is bound to a public-facing interface and the version is in an affected range, making it remotely exploitable
Your environment is affected if the Stormshield SNS version is one of the affected versions listed AND the SSLVPN feature is enabled and exposed to network traffic.
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.
dbcve · scoped3.7.253.11.134.2.10
Upgrade to Stormshield SNS version 3.7.25, 3.11.13, 4.2.10, or 4.3.5 or later. Implement rate limiting on SSLVPN and consider restricting access to trusted IP ranges while planning the upgrade.
3.7.25 (for 3.0.x-3.7.x) | 3.11.13 (for 3.8.x-3.11.x) | 4.2.10 (for 4.0.x-4.2.x) | 4.3.5 (for 4.3.x)
- Identify the current SNS version via admin console or CLI
- Determine the appropriate upgrade path based on current version branch
- Schedule a maintenance window for the firewall upgrade
- Backup the current configuration
- Upgrade to the minimum fixed version for your branch: 3.7.25, 3.11.13, 4.2.10, or 4.3.5
- Verify the upgrade completed successfully
- Confirm firewall accessibility and SSLVPN functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23989 — 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-2022-23989 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