Security readout for executives and security teams
Plain-English summary
SonicWall GMS and Analytics used an outdated encryption algorithm with a hardcoded key to protect sensitive data. If someone can obtain the encrypted data, the protection may be weak or predictable. The sources do not provide CVSS scoring, exploit details, or confirmed active exploitation.
Executive priority
Treat this as a confidentiality risk requiring timely remediation, especially where GMS or Analytics stores credentials or other sensitive operational data. Priority rises if affected systems are broadly accessible or poorly segmented.
Technical view
CVE-2023-34130 is a CWE-327 cryptographic weakness in SonicWall GMS 9.3.2-SP1 and earlier, and Analytics 2.5.0.4-R7 and earlier. The products used TEA with a hardcoded key for sensitive data encryption, undermining confidentiality of protected values if encrypted material is accessible.
Likely exposure
Organizations running SonicWall GMS 9.3.2-SP1 or earlier, or Analytics 2.5.0.4-R7 or earlier, should consider themselves potentially exposed. Exposure depends on whether attackers can access stored encrypted sensitive data or related system files.
Exploitation context
The supplied sources do not report active exploitation, public exploit availability, or KEV listing. Risk is primarily confidentiality loss from weak cryptographic design, not a confirmed remote compromise path in the provided evidence.
Researcher notes
The source bundle lacks CVSS, fixed-version details, attack prerequisites, and exploit confirmation. Analysis should stay focused on cryptographic exposure from TEA plus hardcoded key use, and validation should rely on asset versioning and SonicWall advisory guidance.
Mitigation direction
- Identify any deployed SonicWall GMS and Analytics versions.
- Review SonicWall PSIRT advisory SNWLID-2023-0010 for vendor remediation guidance.
- Upgrade affected products if SonicWall provides supported fixed releases.
- Restrict access to systems and data stores holding encrypted sensitive data.
- Plan secret rotation after remediation if protected values may have been exposed.
Validation and detection
- Inventory SonicWall GMS and Analytics assets and versions.
- Confirm whether versions are at or below the affected releases.
- Review vendor advisory details for fixed versions and prerequisites.
- Check whether encrypted sensitive data was accessible to untrusted users.
- Document remediation status and any required secret rotation decisions.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-327: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2023-34130 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2023-0010CVE reference · vendor-advisory
- https://www.sonicwall.com/support/notices/230710150218060CVE reference · related
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of a Broken or Risky Cryptographic Algorithm
Use of a Broken or Risky Cryptographic Algorithm represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.