CVE-2025-27829
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 · uneditedAn issue was discovered in Stormshield Network Security (SNS) 4.3.x before 4.3.35. If multicast streams are enabled on different interfaces, it may be possible to interrupt multicast traffic on some of these interfaces. That could result in a denial of the multicast routing service on the firewall.
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 confidenceA denial of service vulnerability in Stormshield SNS 4.3.x allows interruption of multicast traffic on certain interfaces when multicast streams are enabled across multiple interfaces, causing failure of the multicast routing service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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 Stormshield SNS versionRun 'clish -c "show version"' or check the product information in the Stormshield admin interface to confirm the installed SNS versionAffected if The installed version is 4.3.x and is lower than 4.3.35 (the patch was released in version 4.3.35)
-
Verify multicast routing is enabledCheck the firewall configuration for multicast routing settings, typically found in the network or routing sections of the SNS admin interface, or run 'multicast status' if available via CLIAffected if Multicast routing is enabled and operational on the firewall
-
Confirm multicast streams across multiple interfacesReview the multicast stream configuration to determine if multicast traffic is being routed between two or more distinct interfaces (not just on a single interface)Affected if Multicast streams are configured to flow across multiple interfaces simultaneously, enabling the condition that triggers the service failure
-
Cross-reference version with vulnerability scopeCompare your confirmed version (from step 1) against the affected range: 4.3.0 through 4.3.34 are vulnerable; versions 4.3.35 and later are patchedAffected if The firewall runs any version from 4.3.0 to 4.3.34 with multicast routing active across multiple interfaces
You are affected if your Stormshield SNS runs version 4.3.0 through 4.3.34 AND you have multicast routing enabled across multiple interfaces simultaneously.
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 · scopedUpgrade to Stormshield SNS version 4.3.35 or later to patch this vulnerability, and review multicast routing configurations on production firewalls.
Stormshield Network Security (SNS) 4.3.35 or later
- 1. Back up the current Stormshield Network Security configuration before initiating any upgrade
- 2. Verify the current SNS version is 4.3.x by checking the system information in the administration interface
- 3. Download SNS version 4.3.35 or later from the official Stormshield support portal (requires valid support contract)
- 4. Review Stormshield release notes for version 4.3.35 to confirm multicast routing improvements are included
- 5. Apply the firmware upgrade following Stormshield's standard upgrade procedure (typically via the administration web interface or CLI)
- 6. After upgrade completion, verify multicast routing functionality is restored and the vulnerability is resolved
- 7. Confirm the running version is 4.3.35 or later in the system information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27829 — 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-2025-27829 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