dbcve.org
Mozart Next 100 FirmwareOperating system · Dbbroadcast

CVE-2025-66262

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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
Arbitrary File Overwrite via Tar Extraction Path Traversal in DB Electronica Telecomunicazioni S.p.A. Mozart FM Transmitter versions 30, 50, 100, 300, 500, 1000, 2000, 3000, 3500, 6000, 7000 allows an attacker to perform Tar extraction with -C / allow arbitrary file overwrite via crafted archive. The `restore_mozzi_memories.sh` script extracts user-controlled tar archives with `-C /` flag, depositing contents to the filesystem root without path validation. When combined with the unauthenticated file upload vulnerabilities (CVE-01, CVE-06, CVE-07), attackers can craft malicious .tgz archives containing path-traversed filenames (e.g., `etc/shadow`, `var/www/index.php`) to overwrite critical system files in writable directories, achieving full system compromise.

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

The restore_mozzi_memories.sh script extracts user-controlled tar archives using the `-C /` flag, which writes extracted contents directly to the filesystem root without validating file paths. Attackers can exploit this by uploading malicious .tgz archives containing path-traversed filenames (e.g., ../../../etc/shadow) to overwrite critical system files and achieve full system compromise.

MitigationImplement strict path validation to prevent path traversal (e.g., rejecting entries with '..' or absolute paths), avoid extracting to filesystem root, and use secure temporary directories with subsequent file move operations. Alternatively, remove or restrict the restore functionality if not required.

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
Mozart Next 100 FirmwareOperating system
Affected:all versions
Mozart Next 1000 FirmwareOperating system
Affected:all versions
Mozart Next 2000 FirmwareOperating system
Affected:all versions
Mozart Next 30 FirmwareOperating system
Affected:all versions
Mozart Next 300 FirmwareOperating system
Affected:all versions
Mozart Next 3000 FirmwareOperating system
Affected:all versions
Mozart Next 3500 FirmwareOperating system
Affected:all versions
Mozart Next 50 FirmwareOperating system
Affected:all versions

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. Confirm device model and firmware
    Identify the Dbbroadcast Mozart Next device (100, 1000, 2000, 30, 300, 3000, 3500, or 50) and note that all firmware versions are affected
    Affected if The device runs any Dbbroadcast Mozart Next firmware version
  2. Locate the restore_mozzi_memories.sh script
    Search the filesystem for the script named restore_mozzi_memories.sh, typically found in /usr/bin/, /sbin/, or within the web application directory
    Affected if The script exists on the device
  3. Inspect the script extraction logic
    Examine the script contents and look for tar extraction commands using the -C / flag without path validation
    Affected if The script uses -C / (or -C flag pointing to root) when extracting user-supplied archives without validating archive paths
  4. Check for path traversal defenses
    Review the script for input validation that rejects '..' sequences or other path traversal patterns in archive filenames before extraction
    Affected if The script lacks validation of archive file paths (no check for '..' or absolute paths)
  5. Verify web upload functionality exposure
    Determine if the device web interface provides an upload feature for tar archives that feeds into the restore_mozzi_memories.sh script
    Affected if Unauthenticated file upload to the restore script is exposed on the network

The device is affected if it is any Dbbroadcast Mozart Next model and the restore_mozzi_memories.sh script extracts archives to the root directory without validating archive paths.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict path validation to prevent path traversal (e.g., rejecting entries with '..' or absolute paths), avoid extracting to filesystem root, and use secure temporary directories with subsequent file move operations. Alternatively, remove or restrict the restore functionality if not required.

Fix this in Mozart Next 100 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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