dbcve.org
Link Following (Symlink)Weakness · CWE-59

CVE-2024-12216

HIGH · 7.1 CVSS v3.0 Published 2025-03-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
No privileges

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
A vulnerability in the `ImageClassificationDataset.from_csv()` API of the `dmlc/gluon-cv` repository, version 0.10.0, allows for arbitrary file write. The function downloads and extracts `tar.gz` files from URLs without proper sanitization, making it susceptible to a TarSlip vulnerability. Attackers can exploit this by crafting malicious tar files that, when extracted, can overwrite files on the victim's system via path traversal or faked symlinks.

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 ImageClassificationDataset.from_csv() API in gluon-cv 0.10.0 downloads tar.gz archives from user-controlled URLs and extracts them without sanitizing file paths within the archive. This TarSlip vulnerability allows attackers to craft malicious archives containing files with path traversal sequences (e.g., ../../etc/passwd) or symlinks pointing to arbitrary locations, enabling arbitrary file write on the victim's filesystem during extraction.

MitigationImplement path validation during tar extraction by checking for path traversal sequences and resolving symlinks before extraction. Use allowlist-based validation or extract to a sandboxed temporary directory first, then move files to the intended destination.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/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. Verify gluon-cv installation and version
    Run 'pip show gluon-cv' or 'pip list | grep gluon' to check if gluon-cv is installed. Confirm the version is 0.10.0.
    Affected if gluon-cv version 0.10.0 is installed
  2. Identify use of from_csv API
    Search codebase for 'ImageClassificationDataset.from_csv' or 'from gluoncv.data import ImageClassificationDataset' patterns in Python files.
    Affected if Code imports and uses ImageClassificationDataset.from_csv() method
  3. Check for URL parameter in from_csv calls
    Review all from_csv() calls to see if they pass a URL argument, particularly from configuration files, user input, or external sources.
    Affected if from_csv() is called with a URL parameter, especially from untrusted or configurable sources
  4. Inspect extraction destination
    Check the directory where datasets are extracted. Look for writable locations like home directories, shared folders, or application directories.
    Affected if Extraction target is a writable directory accessible to the application
  5. Look for path traversal or symlink creation indicators
    After running from_csv with a new URL source, inspect extracted contents using 'tar tzvf archive.tar.gz | head -20' to examine file paths for '../' sequences or symlink entries.
    Affected if Extracted archive contains files with '../' path components or symbolic links pointing outside the intended directory

A system is affected if gluon-cv version 0.10.0 is installed and code uses ImageClassificationDataset.from_csv() with URLs from potentially untrusted sources, leading to extraction in a writable location.

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

Implement path validation during tar extraction by checking for path traversal sequences and resolving symlinks before extraction. Use allowlist-based validation or extract to a sandboxed temporary directory first, then move files to the intended destination.

Recommended fix Moderate confidence

gluon-cv version 0.10.1 or later (check PyPI for latest stable release)

  1. 1. Check current gluon-cv version: pip show gluon-cv
  2. 2. If version is 0.10.0, upgrade to latest version: pip install --upgrade gluon-cv
  3. 3. Alternatively, specify a version newer than 0.10.0: pip install gluon-cv>=0.10.1
  4. 4. Verify the upgrade was successful: pip show gluon-cv
  5. 5. If the ImageClassificationDataset.from_csv() API is used, ensure any downloaded tar files are from trusted sources only until the upgrade is complete
Caveat Review any code changes between 0.10.0 and the target version for API compatibility

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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