CVE
Zipline arbitrary file read in user data export endpoint
- Exploited
- No known exploitation
- Fix
- Fixed in 3.7.10
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Zipline versions from 3.4.5 before 3.7.10 are affected.
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.95% · 61st percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 16/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Zipline, a file-sharing application from diced, has a path traversal flaw in its user data export endpoint through the name query parameter. A remote attacker with a low-privilege login can use directory traversal sequences to read arbitrary files on the server host.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Zipline versions from 3.4.5 before 3.7.10 contain a path traversal vulnerability in the user data export endpoint via the name query parameter. Authenticated attackers can bypass the user id check and use directory traversal sequences to read arbitrary files on the server host.
Who should check
Teams running diced zipline (ghcr.io/diced/zipline) from 3.4.5 before 3.7.10 that expose the user export endpoint.
Read the source excerpt
“Affecting Zipline >=3.4.5, a path traversal vulnerability has been present in the user data exporter”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.3/10CVSS 8.3
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Zipline versions from 3.4.5 before 3.7.10 are affected.Upgrade to a fixed version: 3.7.10.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2024-58404 (Zipline 3.4.5 before 3.7.10 Path Traversal via user export endpoint), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2024-58404 (entry last updated 2026-11-13):
Affected:
- diced zipline: from 3.4.5, fixed in 3.7.10
Fixed versions: 3.7.10.
Conditions (all must be true for the bug to be hit):
- Zipline versions from 3.4.5 before 3.7.10 are affected. (source: https://github.com/diced/zipline/security/advisories/GHSA-v38v-92cm-6mx8)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2024-58404 is not listed as of cve.now's last read.
This KEV status is for CVE-2024-58404 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/diced/zipline/security/advisories/GHSA-v38v-92cm-6mx8
- https://www.vulncheck.com/advisories/zipline-3.4.5-before-3.7.10-path-traversal-via-user-export-endpoint
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2024-58404
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2024-58404"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- diced zipline
From 3.4.5 · fixed in 3.7.10
Evidence 4
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2024-58404
Is CVE-2024-58404 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A path traversal flaw in Zipline's user data exporter lets an authenticated user read arbitrary files on the server host, such as /etc/passwd.Source: github.com
Which versions are affected by CVE-2024-58404?
zipline: from 3.4.5 before 3.7.10.Source: cve.now feed data
Am I affected, and how do I check?
Zipline versions from 3.4.5 before 3.7.10 are affected, based on the advisory's stated range. To check a install, look up the Zipline version it runs and compare it against that range.Source: github.com
How do I fix CVE-2024-58404?
The facts provided do not name a fixed version or vendor patch, so no specific upgrade target can be given from them. Check the Zipline project's release notes for a version at or beyond 3.7.10 for guidance.Source: github.com