CVE-2022-22277
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 · uneditedA vulnerability in SonicOS SNMP service resulting exposure of Wireless Access Point sensitive information in cleartext.
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 vulnerability in the SonicOS SNMP service allows exposure of Wireless Access Point sensitive information in cleartext. The SNMP service transmits sensitive configuration or credential data without encryption, enabling an unauthenticated network attacker to intercept this information.
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< 6.5.4.10= 7.0.0< 6.5.4.10= 7.0.0< 6.5.4.10= 7.0.0< 6.5.4.10= 7.0.0< 7.0.1.0< 7.0.1.0< 7.0.1.0< 7.0.1.0CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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 the Sonicwall device modelLog into the Sonicwall management interface and navigate to System > Status to view the appliance model name (e.g., Tz300, Nssp 11700)Affected if The model matches one of the affected products: Tz300p, Tz300w, Tz350, Tz350w, Nssp 10700, Nssp 11700, Nssp 12400, or Nssp 12800
-
Check the installed firmware versionIn the Sonicwall management interface, go to System > Status and locate the Firmware Version fieldAffected if For Tz300p/Tz300w/Tz350/Tz350w: version is below 6.5.4.10 or equals 7.0.0. For Nssp 10700/11700/12400/12800: version is below 7.0.1.0
-
Verify if SNMP service is enabledIn the Sonicwall management interface, navigate to System > SNMP and check if Enable SNMP is checked/enabledAffected if SNMP service is enabled on the device
-
Determine the SNMP version in useIn the SNMP settings page, check which SNMP version is configured (v1/v2c or v3) and whether AuthPriv security level is selected for v3Affected if SNMP is configured using v1 or v2c, or v3 is used without AuthPriv (no encryption)
-
Confirm if Wireless Access Point management is configuredIn the Sonicwall interface, check if Wireless > Access Points or similar wireless management settings are configured and enabledAffected if Wireless AP management is enabled and the device is using the vulnerable SNMP configuration
The device is affected if it is one of the listed models, runs a firmware version in the vulnerable range, has SNMP enabled with v1/v2c or v3 without encryption, and has wireless access point management configured.
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 · scoped6.5.4.107.0.1.0
Implement SNMPv3 with encryption (AuthPriv security level) or disable SNMP if not required, and restrict SNMP access to authorized management networks.
Tz series: 6.5.4.10 or later (or 7.0.1+ if moving to 7.x); NSSP series: 7.0.1.0 or later
- 1. Identify the exact SonicWall device model (Tz300p, Tz300w, Tz350, Tz350w, Nssp 10700, Nssp 11700, Nssp 12400, or Nssp 12800)
- 2. Access the SonicWall device management interface or CLI
- 3. Navigate to the Firmware Update or System > Settings section
- 4. Download the appropriate firmware from the official SonicWall support portal (support.sonicwall.com)
- 5. Upload and install the firmware upgrade to a fixed version (6.5.4.10 or later for Tz series; 7.0.1.0 or later for NSSP series)
- 6. After upgrade, verify the SNMP service configuration and confirm sensitive information is no longer exposed
- 7. Test that wireless access point functionality remains operational post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.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,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22277 — 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-22277 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