dbcve.org
SonicosOperating system · Sonicwall

CVE-2023-39276

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 post-authentication stack-based buffer overflow vulnerability in the getBookmarkList.json URL endpoint 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 exists in SonicOS firewall firmware in the getBookmarkList.json endpoint. The flaw is post-authentication, requiring valid credentials to exploit, and can cause the firewall to crash.

MitigationApply the vendor-supplied SonicOS firmware update to patch the vulnerability. Until patched, limit access to the management interface to trusted networks only.

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. Check installed SonicOS firmware version
    Access the firewall management interface and navigate to System > Status or use the 'show version' command via CLI (SSH or console). Note the exact firmware version string displayed.
    Affected if The installed version is lower than 7.0.1-5145, or lower than 6.5.4.4-44v-21-2340, or lower than 6.5.4.13-105n (depending on your major release branch)
  2. Identify the major Sonicos release branch
    Examine the firmware version string: versions starting with 7.x indicate the 7.0.x branch, versions starting with 6.5.4.x indicate the 6.5.4.x branch. Determine which branch your firewall is running.
    Affected if You are running any 6.5.4.x version below 6.5.4.13-105n or below 6.5.4.4-44v-21-2340, or any 7.0.x version below 7.0.1-5145
  3. Verify management interface accessibility
    Determine if the SonicWall management interface (HTTPS on port 443 or HTTP on port 80) is reachable from untrusted networks. Check firewall access rules and NAT policies.
    Affected if The management interface is exposed to networks outside your trusted internal network (since the vulnerability is post-authentication but can crash the firewall)

You are affected if your installed SonicOS version is below 7.0.1-5145 (for 7.0.x releases), below 6.5.4.4-44v-21-2340 (for 6.5.4.0-3.x releases), or below 6.5.4.13-105n (for 6.5.4.4+ releases), and the management interface is accessible to potential attackers.

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-supplied SonicOS firmware update to patch the vulnerability. Until patched, limit access to the management interface to trusted networks only.

Recommended fix High confidence

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

  1. 1. Identify the current Sonicos version running on the affected SonicWall firewall
  2. 2. Determine which version branch is in use (7.x, 6.5.4.4, or 6.5.4.13)
  3. 3. Download the appropriate fixed release from the SonicWall support portal: 7.0.1-5145 or higher for 7.x branch; 6.5.4.4-44v-21-2340 or higher for 6.5.4.4 branch; 6.5.4.13-105n or higher for 6.5.4.13 branch
  4. 4. Back up the current firewall configuration
  5. 5. Upload and install the firmware upgrade via the SonicWall management interface
  6. 6. After upgrade, verify the firewall is operational and the vulnerability is resolved
  7. 7. Confirm the new firmware version matches or exceeds the fixed releases
Caveat Review SonicWall release notes for any configuration or feature changes between current and target versions before upgrading

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-39276 — 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-39276 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