dbcve.org
SonicosOperating system · Sonicwall

CVE-2023-39280

MEDIUM · 6.5 CVSS v3.1 Published 2023-10-17
Fix available
A fix is available. Upgrade to 6.5.4.4-44v-21-2340 / 6.5.4.13-105n or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
SonicOS p ost-authentication Stack-Based Buffer Overflow vulnerability in the ssoStats-s.xml, ssoStats-s.wri URL endpoints leads to a firewall 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 · moderate confidence

A stack-based buffer overflow vulnerability in SonicOS firewall exists in the ssoStats-s.xml and ssoStats-s.wri URL endpoints. The flaw is triggered after successful authentication, allowing an authenticated attacker to send specially crafted requests that overflow a stack buffer, causing the firewall to crash.

MitigationApply the vendor patch from SonicWall when available. Until then, restrict access to the affected endpoints to trusted IP addresses only via firewall access rules, and enforce strong authentication credentials for all administrative accounts.

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
SonicosOperating system
Affected:< 7.0.1-5145< 6.5.4.4-44v-21-2340< 6.5.4.13-105n

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify SonicOS version
    Access the firewall admin interface and navigate to System > Status, or use the CLI command 'show version' to retrieve the installed SonicOS firmware version.
    Affected if The installed version is less than 7.0.1-5145, or less than 6.5.4.4-44v-21-2340, or less than 6.5.4.13-105n.
  2. Confirm remote admin access is enabled
    Check the firewall's management access settings under Network > Interfaces or via CLI command 'show management' to see if HTTPS/SSH management is enabled on external interfaces.
    Affected if Remote administrative access is permitted on any WAN-facing interface.
  3. Verify the vulnerable endpoints are accessible
    Attempt to access https://<firewall-ip>/ssoStats-s.xml and https://<firewall-ip>/ssoStats-s.wri from a remote location, or check the URL filtering/allowed requests configuration.
    Affected if These endpoints are reachable from untrusted networks without IP restriction.
  4. Review admin account authentication method
    Check the local user database and authentication settings under Users > Local Users or AAA settings to determine if strong passwords and lockout policies are enforced.
    Affected if Weak or default authentication credentials are in use, or no account lockout policy is configured.

You are affected if your SonicOS version falls below the three version thresholds AND the vulnerable endpoints are accessible to untrusted users.

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 6.5.4.4-44v-21-2340 / 6.5.4.13-105n / 7.0.1-5145 or later
Fixed in 6.5.4.4-44v-21-23406.5.4.13-105n7.0.1-5145
Interim mitigation

Apply the vendor patch from SonicWall when available. Until then, restrict access to the affected endpoints to trusted IP addresses only via firewall access rules, and enforce strong authentication credentials for all administrative accounts.

Recommended fix High confidence

SonicOS 7.0.1-5145 (or later 7.x); 6.5.4.4-44v-21-2340 (or later); 6.5.4.13-105n (or later)

  1. 1. Identify the current SonicOS version running on the SonicWall firewall via the management interface or CLI (show version)
  2. 2. Determine which version branch the current firmware is on (7.x or 6.5.4.x)
  3. 3. For SonicOS 7.x: Upgrade to version 7.0.1-5145 or later
  4. 4. For SonicOS 6.5.4.4 branch: Upgrade to version 6.5.4.4-44v-21-2340 or later
  5. 5. For SonicOS 6.5.4.13 branch: Upgrade to version 6.5.4.13-105n or later
  6. 6. After upgrading, verify the version change was successful and test that the firewall is functioning normally
  7. 7. Confirm the ssoStats-s.xml and ssoStats-s.wri endpoints are no longer vulnerable
Caveat Standard firmware upgrade considerations apply - backup configuration before upgrade, plan for brief downtime, and verify compatibility with any connected devices or VPN peers

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

Fix this in Sonicos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
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,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-39280 — 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-39280 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