dbcve.org
Truenas FirmwareOperating system · Ixsystems

CVE-2024-11944

HIGH · 8.8 CVSS v3.1 Published 2024-12-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
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
iXsystems TrueNAS CORE tarfile.extractall Directory Traversal Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of iXsystems TrueNAS devices. Authentication is not required to exploit this vulnerability. The specific flaw exists within the tarfile.extractall method. The issue results from the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this in conjunction with other vulnerabilities to execute code in the context of root. Was ZDI-CAN-25626.

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 vulnerability exists in the tarfile.extractall method within iXsystems TrueNAS CORE, where user-supplied paths are not properly validated before file operations. This allows directory traversal attacks via specially crafted tar archives containing paths with '../' sequences. An unauthenticated network-adjacent attacker can exploit this to write files to arbitrary locations on the system, achieving root-level code execution.

MitigationApply the official iXsystems TrueNAS CORE security patch when available. Until then, restrict network access to TrueNAS management interfaces and disable any unauthenticated file extraction services.

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
Truenas FirmwareOperating system
Affected:= 13.0

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

CVSS:3.1/AV:A/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 TrueNAS CORE is running
    Log into the TrueNAS web UI or run 'glxdd status' from the shell to identify the installed system as TrueNAS CORE.
    Affected if The system is not TrueNAS CORE (e.g., TrueNAS SCALE, another NAS platform).
  2. Verify the exact firmware version
    Navigate to System > Overview in the web UI or run 'freenas-version' from the shell to determine the installed firmware version.
    Affected if The firmware version is exactly 13.0. Versions other than 13.0 are not affected by this specific CVE.
  3. Identify services accepting tar archives from network sources
    Review enabled services in the web UI under Services > API Services and check for any custom configurations or scripts that invoke the Python tarfile module with extractall().
    Affected if Any service accepts tar archives from unauthenticated network sources and processes them using tarfile.extractall without path validation.
  4. Audit custom scripts or plugins using tar extraction
    Examine any user-created scripts, plugins, or third-party integrations in /usr/local/etc/rc.d/, /etc/ix/ or the plugins directory for usage of tarfile.extractall().
    Affected if Custom code calls tarfile.extractall() on archives obtained from untrusted network sources without sanitizing extracted paths.
  5. Check for exposed management interfaces
    Review network access controls in the web UI under Network > Global Settings and verify that TrueNAS management ports (HTTP/HTTPS, SSH) are not exposed to unauthenticated network-adjacent attackers.
    Affected if Management interfaces are accessible to unauthenticated attackers on the network.

A system is affected if it is TrueNAS CORE firmware version 13.0 AND has any service or script that uses tarfile.extractall() on archives from unauthenticated network sources without validating paths for '../' sequences.

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

Apply the official iXsystems TrueNAS CORE security patch when available. Until then, restrict network access to TrueNAS management interfaces and disable any unauthenticated file extraction services.

Fix this in Truenas 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-2024-11944 — 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-2024-11944 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