dbcve.org
AnalyticsApplication · Sonicwall

CVE-2023-34129

HIGH · 8.8 CVSS v3.1 Published 2023-07-13
Fix available
A fix is available. Upgrade to 9.3.2 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Improper limitation of a pathname to a restricted directory ('Path Traversal') vulnerability in SonicWall GMS and Analytics allows an authenticated remote attacker to traverse the directory and extract arbitrary files using Zip Slip method to any location on the underlying filesystem with root privileges. This issue affects GMS: 9.3.2-SP1 and earlier versions; Analytics: 2.5.0.4-R7 and earlier versions.

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 confidence

A path traversal vulnerability in SonicWall GMS and Analytics allows authenticated remote attackers to use the Zip Slip method to extract arbitrary files to any location on the filesystem with root privileges by manipulating file paths during import operations.

MitigationUpgrade to GMS version 9.3.2-SP2 or later and Analytics version 2.5.0.4-R8 or later. If patching is immediately infeasible, restrict administrative access to trusted networks and monitor for suspicious import activity.

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
AnalyticsApplication
Affected:<= 2.5.0.4-r7
Global Management SystemApplication
Affected:< 9.3.2= 9.3.2

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 installed SonicWall product and version
    Check the installed version by logging into the web interface and navigating to the About or System Information page, or run: 'grep -i version /opt/sonicwall/gms/VERSION' or 'grep -i version /opt/sonicwall/analytics/VERSION' depending on the installation path.
    Affected if The installed version is SonicWall GMS < 9.3.2, exactly 9.3.2, or SonicWall Analytics <= 2.5.0.4-r7
  2. Confirm administrative web interface is accessible
    Verify the GMS or Analytics web management console is reachable over HTTPS/HTTP on ports 443 or 80. Check if the /gms or /analytics endpoints respond.
    Affected if The administrative interface is exposed and reachable, which is required for the authenticated attacker to exploit the import function
  3. Verify import functionality is enabled
    Log into the administrative console and navigate to the Import/Export settings or Backup/Restore section. Look for options to import configuration files, reports, or device data.
    Affected if The import functionality is available and accessible to authenticated users, which is the attack vector for the Zip Slip vulnerability
  4. Review audit logs for suspicious import activity
    Check system logs and GMS/Analytics audit logs for import operations with abnormally long or nested file paths. Look for entries containing '../' patterns or references to unexpected extraction paths. Typical log locations: /opt/sonicwall/gms/logs/audit.log or /var/log/sonicwall/gms/audit.log.
    Affected if Logs show import operations extracting files to locations outside the expected application directories, indicating exploitation attempts

Your environment is affected if you are running GMS versions below 9.3.2-SP2 or exactly 9.3.2, or Analytics version 2.5.0.4-r7 or earlier, and the administrative web interface with import functionality is accessible to authenticated 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 9.3.2 or later
Fixed in 9.3.2
Interim mitigation

Upgrade to GMS version 9.3.2-SP2 or later and Analytics version 2.5.0.4-R8 or later. If patching is immediately infeasible, restrict administrative access to trusted networks and monitor for suspicious import activity.

Recommended fix Moderate confidence

GMS: 9.3.2-SP2 or later; Analytics: 2.5.0.4-R8 or later

  1. 1. Identify the current version of SonicWall GMS or Analytics by checking the About section in the product interface
  2. 2. For GMS: Upgrade to version 9.3.2-SP2 or later as released by SonicWall
  3. 3. For Analytics: Upgrade to version 2.5.0.4-R8 or later as released by SonicWall
  4. 4. After upgrade, verify the new version is running and the vulnerability is resolved
  5. 5. Review SonicWall release notes and patch documentation for any additional requirements
Caveat Review release notes for any configuration changes or migration steps required when upgrading

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

Fix this in Analytics Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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