CVE-2021-28665
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 · uneditedStormshield SNS with versions before 3.7.18, 3.11.6 and 4.1.6 has a memory-management defect in the SNMP plugin that can lead to excessive consumption of memory and CPU resources, and possibly 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 confidenceStormshield SNS versions before 3.7.18, 3.11.6, and 4.1.6 contain a memory-management defect in the SNMP plugin that allows excessive consumption of memory and CPU resources, potentially leading to denial of service. The vulnerability stems from improper memory handling within the SNMP plugin component.
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.18>= 3.8.0, < 3.11.5>= 4.0.0, < 4.1.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.
-
Identify installed Stormshield SNS versionUse the system CLI or admin interface to retrieve the current firmware version (for example, by running 'nsasm -v' or checking the dashboard in the web admin panel)Affected if The installed version falls within any of these ranges: >= 3.0.0 and < 3.7.18; >= 3.8.0 and < 3.11.6; >= 4.0.0 and < 4.1.6
-
Confirm SNMP plugin is activeCheck the Stormshield configuration for the SNMP service status (for example, inspect the SNMP daemon or plugin configuration via CLI or web interface)Affected if The SNMP plugin is enabled and running on the device
-
Verify memory or CPU symptomsMonitor system resources using built-in monitoring tools to observe unusual memory growth or CPU usage spikes, particularly if correlated with SNMP operationsAffected if Excessive memory consumption or high CPU usage is observed, especially in processes related to SNMP
A system is affected if it runs a Stormshield SNS version below 3.7.18, 3.11.6, or 4.1.6 AND has the SNMP plugin enabled, as the vulnerability only triggers when the SNMP component is active.
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.
From vendor data3.7.183.11.54.1.5
Upgrade Stormshield SNS to version 3.7.18, 3.11.6, 4.1.6 or later to remediate the memory-management defect in the SNMP plugin.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-28665 — 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-2021-28665 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