dbcve.org
AnalyticsApplication · Sonicwall

CVE-2023-34130

CRITICAL · 9.8 CVSS v3.1 Published 2023-07-13
Fix available
A fix is available. Upgrade to 9.3.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
SonicWall GMS and Analytics use outdated Tiny Encryption Algorithm (TEA) with a hardcoded key to encrypt sensitive data. 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

SonicWall GMS and Analytics products use the Tiny Encryption Algorithm (TEA), a cryptographically weak algorithm, combined with a hardcoded encryption key to protect sensitive data. This combination allows attackers who obtain the key (through code review, binary analysis, or other means) to decrypt all protected data, potentially exposing credentials, configuration secrets, or other sensitive information.

MitigationReplace the TEA implementation with a modern authenticated encryption algorithm (such as AES-256-GCM) and implement proper key management (e.g., per-instance keys, key rotation, secrets management). Audit and re-encrypt any previously encrypted sensitive data with the new algorithm.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 SonicWall Analytics version
    Check the installed Analytics version by accessing the admin console or running: grep -r 'version' /opt/sonicwall/analytics/etc 2>/dev/null or checking the application manifest
    Affected if version is 2.5.0.4-r7 or lower (e.g., 2.5.0.4-r1 through r7)
  2. Identify SonicWall GMS version
    Check the installed GMS version via the management interface or by examining the installation directory: ls -la /opt/SonicWall/GMS/Version 2>/dev/null or checking the about page in the console
    Affected if version is 9.3.2 or any version below 9.3.2 (e.g., 9.3.0, 9.2.x, earlier)
  3. Locate TEA encryption implementation
    Search the product installation for Tiny Encryption Algorithm code: grep -ri 'tiny.*encrypt' /opt/sonicwall 2>/dev/null or grep -ri 'tea' /opt/sonicwall 2>/dev/null looking for encryption-related files
    Affected if TEA algorithm code or references are found in the installation
  4. Find hardcoded encryption keys
    Search for hardcoded keys in configuration files or embedded in binaries: grep -ri 'encrypt.*key' /opt/sonicwall 2>/dev/null or strings <binary> | grep -i 'key' in the encryption modules
    Affected if a hardcoded or static encryption key is found in configuration, code, or embedded in binaries
  5. Identify encrypted sensitive data
    Examine the database or config storage for encrypted fields: ls -la <installation>/database/ or check for base64-encoded or hex-encoded data in configuration files storing credentials or secrets
    Affected if encrypted credentials, API keys, passwords, or configuration secrets exist in the system that were protected using the weak TEA method

You are affected if you run SonicWall Analytics <= 2.5.0.4-r7 or GMS version 9.3.2 or below, and the product uses TEA encryption with a hardcoded key to protect sensitive data.

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.

From vendor data
Upgrade available Upgrade to 9.3.2 or later
Fixed in 9.3.2
Interim mitigation

Replace the TEA implementation with a modern authenticated encryption algorithm (such as AES-256-GCM) and implement proper key management (e.g., per-instance keys, key rotation, secrets management). Audit and re-encrypt any previously encrypted sensitive data with the new algorithm.

Fix this in Analytics Scoped from the published advisory
  • Consultation6.0 h
  • Implementation20.0 h
  • Testing10.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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