CVE-2022-27812
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 · uneditedFlooding SNS firewall versions 3.7.0 to 3.7.29, 3.11.0 to 3.11.17, 4.2.0 to 4.2.10, and 4.3.0 to 4.3.6 with specific forged traffic, can lead to SNS DoS.
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 confidenceThis is a Denial of Service vulnerability in Fortinet SNS firewall products. An unauthenticated remote attacker can cause a DoS condition by flooding the device with specific forged traffic packets. The vulnerability affects multiple version branches (3.7.x, 3.11.x, 4.2.x, 4.3.x).
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.7.0, < 3.7.30>= 3.11.0, < 3.11.18>= 4.2.0, < 4.2.11>= 4.3.0, < 4.3.7CVSS 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.
-
Identify installed Stormshield SNS versionAccess the SNS administration interface or CLI and run the command to display the system version, typically 'version' or through the dashboard status pageAffected if The displayed version falls within any of these ranges: 3.7.0-3.7.29, 3.11.0-3.11.17, 4.2.0-4.2.10, or 4.3.0-4.3.6
-
Confirm the product modelVerify that the device is a Stormshield Network Security (SNS) firewall product through the administrative interface or device labelingAffected if The device is an SNS firewall model running a version in the affected ranges listed above
-
Check network exposureReview firewall network interface configurations to determine if the SNS device is directly exposed to untrusted networks or the internet, particularly on interfaces listening for external trafficAffected if The device has public-facing network interfaces or accepts traffic from untrusted networks without adequate filtering
-
Review system logs for DoS indicatorsExamine SNS logs for signs of unusual traffic patterns, service interruptions, or CPU/memory exhaustion events that may indicate a DoS conditionAffected if Recent logs show unexpected service disruptions or abnormal traffic spikes matching the DoS attack pattern
A user is affected if their Stormshield SNS firewall runs a version within 3.7.0-3.7.29, 3.11.0-3.11.17, 4.2.0-4.2.10, or 4.3.0-4.3.6 and is network-accessible to potential attackers.
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.303.11.184.2.11
Upgrade SNS firewall to versions beyond the vulnerable ranges: 3.7.30+, 3.11.18+, 4.2.11+, and 4.3.7+ to obtain the patch.
3.7.30 (for 3.7.x branch), 3.11.18 (for 3.11.x branch), 4.2.11 (for 4.2.x branch), or 4.3.7 (for 4.3.x branch)
- Identify the current installed version of Stormshield Network Security (SNS) firewall
- Determine which version branch is in use (3.7.x, 3.11.x, 4.2.x, or 4.3.x)
- Obtain the fixed version from Stormshield's official support portal based on your branch: 3.7.30, 3.11.18, 4.2.11, or 4.3.7
- Review the upgrade documentation and release notes for the target version
- Plan a maintenance window as the upgrade may require firewall restart or brief downtime
- Back up the current SNS configuration before proceeding
- Perform the upgrade to the appropriate fixed version
- Verify system functionality and confirm the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27812 — 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-27812 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