dbcve.org
Stormshield Network SecurityApplication · Stormshield

CVE-2023-47093

MEDIUM · 6.5 CVSS v3.1 Published 2023-12-21
Fix available
A fix is available. Upgrade to 4.3.22 / 4.6.9 or later.
See remediation →
70/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
An issue was discovered in Stormshield Network Security (SNS) 4.0.0 through 4.3.21, 4.4.0 through 4.6.8, and 4.7.0. Sending a crafted ICMP packet may lead to a crash of the ASQ engine.

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 confidence

A crafted ICMP packet causes the ASQ (Application-level Super Queue) engine in Stormshield Network Security to crash, resulting in denial of service. This is a network-based DoS vulnerability affecting SNS versions 4.0.0-4.3.21, 4.4.0-4.6.8, and 4.7.0, exploitable without authentication.

MitigationApply vendor-supplied firmware patches when available. As a compensating control, consider filtering or rate-limiting untrusted ICMP traffic at perimeter defenses until the update can be deployed.

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
Stormshield Network SecurityApplication
Affected:>= 4.0.0, < 4.3.22>= 4.4.0, < 4.6.9= 4.7.0

CVSS 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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Stormshield SNS product installation
    Log into the SNS CLI or admin interface and run 'show version' or check the system information page to identify the product as Stormshield Network Security
    Affected if The product is not Stormshield Network Security (this CVE does not apply)
  2. Check installed SNS version
    Run 'show version' in the SNS CLI or view the version in the admin dashboard. Compare the version number to the affected ranges: 4.0.0-4.3.21, 4.4.0-4.6.8, or 4.7.0
    Affected if The installed version falls within any of the affected version ranges
  3. Verify ICMP exposure to untrusted networks
    Review firewall or network segmentation policies to determine if the SNS device accepts ICMP traffic from external or untrusted networks. Check interface configurations for ICMP permit rules
    Affected if ICMP packets from untrusted sources can reach the SNS device (the attack vector is network-accessible)
  4. Inspect for ASQ engine crash indicators
    Check system logs (/var/log/messages or via 'log read' command) for ASQ-related errors, crashes, or unexpected service restarts, particularly around ICMP traffic processing
    Affected if ASQ crashes or restarts are logged, especially in correlation with ICMP traffic

A user is affected if they are running Stormshield SNS version 4.0.0-4.3.21, 4.4.0-4.6.8, or 4.7.0 and the device accepts ICMP traffic from untrusted networks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 4.3.22 / 4.6.9 or later
Fixed in 4.3.224.6.9
Interim mitigation

Apply vendor-supplied firmware patches when available. As a compensating control, consider filtering or rate-limiting untrusted ICMP traffic at perimeter defenses until the update can be deployed.

Recommended fix High confidence

Minimum fixed versions: 4.3.22, 4.6.9, or 4.7.1 (or later). Choose the latest stable release in your current major branch.

  1. 1. Identify the current SNS version by checking the product interface or running: CLI command 'show system version'
  2. 2. Determine the appropriate upgrade path based on your current version branch (4.3.x, 4.4.x-4.6.x, or 4.7.0)
  3. 3. Back up the current SNS configuration using the backup function in the admin interface or CLI command 'system backup'
  4. 4. Download the appropriate fixed version from the Stormshield customer portal or official distribution channels
  5. 5. Upload the firmware through the SNS admin interface (System > Maintenance > Firmware Update) or via CLI
  6. 6. Verify the upgrade was successful and the ASQ engine is running normally
Caveat Review Stormshield release notes before upgrading; major version jumps may introduce configuration or feature changes requiring adjustments.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Stormshield Network Security Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-47093 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-47093 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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