CVE-2022-30279
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.8. The event logging of the ASQ sofbus lacbus plugin triggers the dereferencing of a NULL pointer, leading to a crash of SNS. An attacker could exploit this vulnerability via forged sofbus lacbus traffic to cause a firmware crash.
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 NULL pointer dereference vulnerability exists in the ASQ sofbus lacbus plugin's event logging functionality in Stormshield Network Security (SNS) versions before 4.3.8. When processing specially crafted sofbus lacbus traffic, the event logging code dereferences a NULL pointer, causing the firmware to crash, resulting in denial of service.
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.3.3, < 4.3.8CVSS 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.
-
Check installed SNS firmware versionAccess the SNS CLI or admin interface and run the command to display the firmware version, typically 'version' or check System > Status in the web UIAffected if The version is 4.3.3, 4.3.4, 4.3.5, 4.3.6, or 4.3.7 (any version >= 4.3.3 but < 4.3.8)
-
Verify ASQ sofbus lacbus plugin statusCheck the ASQ (Application Level QoS / Application Filtering) configuration to determine if the sofbus lacbus plugin is enabled in the filtering policyAffected if The sofbus lacbus plugin is loaded and actively processing traffic in the filtering rules
-
Review system logs for crash eventsExamine the SNS system logs and crash logs for entries related to sofbus lacbus processing failures or NULL pointer dereference errors occurring around the time of unusual trafficAffected if Crash logs or system logs show NULL pointer dereference errors or unexpected daemon restarts linked to the sofbus lacbus plugin
-
Inspect traffic logs for sofbus lacbus trafficCheck the traffic logs or ASQ inspection logs for any processed sofbus lacbus protocol traffic patternsAffected if The device is actively inspecting or processing sofbus lacbus protocol traffic
A system is affected if it runs SNS firmware version 4.3.3 through 4.3.7 and has the ASQ sofbus lacbus plugin enabled while processing sofbus lacbus traffic, which could trigger the NULL pointer dereference crash.
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.3.8
Upgrade Stormshield SNS to version 4.3.8 or later to patch the NULL pointer dereference in the sofbus lacbus plugin.
4.3.8
- Download the SNS firmware version 4.3.8 from the official Stormshield support portal
- Access the Stormshield Network Security administration interface
- Navigate to the firmware update or system maintenance section
- Upload and apply the 4.3.8 firmware update
- Verify the system is running version 4.3.8 after the update completes
- Confirm network services are functioning normally post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30279 — 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-30279 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