dbcve.org
SonicosOperating system · Sonicwall

CVE-2023-39279

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 getPacketReplayData.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's getPacketReplayData.json endpoint. The flaw is post-authentication, requiring valid credentials to exploit, and leads to firewall crash (denial of service). The vulnerability stems from improper bounds checking when handling input in the JSON endpoint, allowing a specially crafted request to overflow a stack buffer.

MitigationApply vendor-provided patches for CVE-2023-39279 when available. Until then, restrict management interface access to trusted IP addresses via VPN or ACLs, enforce strong authentication credentials, and monitor for unusual administrative sessions.

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 management interface and navigate to System > Status, or use CLI command 'show version' or 'get system status' to retrieve the installed firmware version.
    Affected if The installed version is below 7.0.1-5145, below 6.5.4.4-44v-21-2340, or below 6.5.4.13-105n.
  2. Confirm management interface exposure
    Review firewall access rules or NAT configurations to determine if the management interface (HTTPS port 443) is accessible from untrusted networks such as the public internet.
    Affected if The management interface is reachable from untrusted IP addresses without VPN or ACL restrictions.
  3. Check for endpoint access logs
    Review firewall logs, especially under Log > System or Log > Events, for any requests to /getPacketReplayData.json endpoint from administrative sessions.
    Affected if Requests to the getPacketReplayData.json endpoint are logged, indicating the feature is in use.
  4. Verify SNMP version disclosure
    If SNMP is enabled, query the firewall using snmpwalk or snmpget to retrieve system information and confirm the firmware version is exposed.
    Affected if SNMP responses disclose a version matching the affected ranges.

You are affected if your SonicOS firmware version falls below the patched releases AND your management interface is accessible to untrusted networks where an attacker could authenticate and send crafted requests to the getPacketReplayData.json endpoint.

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 vendor-provided patches for CVE-2023-39279 when available. Until then, restrict management interface access to trusted IP addresses via VPN or ACLs, enforce strong authentication credentials, and monitor for unusual administrative sessions.

Recommended fix High confidence

SonicOS 7.0.1-5145, 6.5.4.4-44v-21-2340, or 6.5.4.13-105n (depending on your baseline branch)

  1. Identify the current SonicOS version running on the affected firewall appliance
  2. Navigate to the SonicWall support portal or use the administrative interface to check for available firmware updates
  3. If running SonicOS version < 7.0.1, upgrade to version 7.0.1-5145 or later
  4. If running SonicOS 6.5.4.4.x versions, upgrade to version 6.5.4.4-44v-21-2340 or later
  5. If running SonicOS 6.5.4.13.x versions, upgrade to version 6.5.4.13-105n or later
  6. After upgrading, verify the new version is installed correctly
  7. Test that the firewall functionality is operational post-upgrade
  8. Restrict administrative access to trusted IP addresses to reduce attack surface until patch is applied

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

Fix this in Sonicos Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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