CVE-2023-26095
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 · uneditedASQ in Stormshield Network Security (SNS) 4.3.15 before 4.3.16 and 4.6.x before 4.6.3 allows a crash when analysing a crafted SIP packet.
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 denial of service vulnerability exists in the ASQ analysis engine of Stormshield Network Security (SNS) firewalls. An unauthenticated remote attacker can send a specially crafted SIP packet to the firewall, causing the ASQ analysis component to crash and potentially rendering the security device unavailable.
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>= 4.6.0, < 4.6.3= 4.3.15CVSS 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 SNS firmware versionAccess the Stormshield administration interface or run 'clish -c "show version"' via SSH to display the installed SNS firmware version.Affected if The installed version is >= 4.6.0 and < 4.6.3, or exactly 4.3.15.
-
Locate the ASQ analysis configurationIn the Stormshield web interface, navigate to Configuration > Analysis Engine > ASQ or check the CLI command 'asq show' to view ASQ module settings.Affected if The ASQ analysis engine is enabled on the device.
-
Verify SIP inspection is activeCheck the SIP security policy or filter configuration via the web UI under Firewall > Filter or run 'filter show' in CLI to see if SIP protocol inspection is defined.Affected if A filter rule or inspection policy explicitly processes SIP traffic through the ASQ engine.
-
Confirm SIP traffic is permittedReview active connections or traffic logs for SIP (port 5060/UDP or TCP) using 'connlog' or the monitoring dashboard to see if SIP packets are reaching the ASQ component.Affected if SIP traffic flows through the firewall and is being analyzed by the ASQ engine.
You are affected if your SNS version falls within 4.3.15 or 4.6.0 through 4.6.2 and the ASQ engine is actively processing SIP 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 · scoped4.6.3
Upgrade Stormshield SNS to version 4.3.16 or 4.6.3 or later to resolve the vulnerability. As a temporary workaround, consider filtering or rate-limiting SIP traffic at the network perimeter until the patch can be applied.
4.3.16 or later for 4.3.15; 4.6.3 or later for 4.6.x
- 1. Check current Stormshield Network Security (SNS) version via the management interface or CLI
- 2. If running version 4.3.15, plan upgrade to version 4.3.16 or later
- 3. If running version 4.6.0 through 4.6.2, plan upgrade to version 4.6.3 or later
- 4. Schedule maintenance window for the upgrade procedure
- 5. Perform upgrade following Stormshadow standard upgrade procedures
- 6. Verify the new version is installed and ASQ functionality is operational
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-26095 — 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-2023-26095 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