CVE
Zipline authorization bypass in registration endpoint
Only affects Zipline through 3.7.9 when both invites and user registration are enabled. No fixed version is named in the checked facts.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Both invites (FEATURES_INVITES) and user registration (FEATURES_USER_REGISTRATION) are enabled. Zipline version through 3.7.9.
- 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.37% · 31st 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? →
- 26/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 through 3.7.9 has an improper authorization flaw in its registration endpoint, which checks invite codes only when user registration is disabled, so accounts can be created without an invite when both invites and registration are enabled. An attacker can exploit this remotely, without logging in, by sending a direct request that omits the invite code to create accounts, view stats, and exhaust storage by uploading many files.
Read the original description
Zipline through 3.7.9 contains an improper authorization vulnerability in the /api/auth/register endpoint, which enforces invite codes only when user registration is disabled, so registration succeeds without an invite when both invites and user registration are enabled. Unauthenticated attackers can send a direct POST request omitting the invite code to create accounts, view stats, and exhaust storage by uploading many files.
Who should check
Teams self-hosting Zipline 3.7.9 or earlier with both invites and user registration enabled, such as sysadmins running public Zipline instances.
Read the source excerpt
“registration succeeds without an invite when both invites and user registration are enabled”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.8/10CVSS 8.8
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 76 if added to CISA KEV
- Would score about 71 if CISA's SSVC rates exploitation active
What to do
Check whether your setup matches what the bug needs.
Both invites (FEATURES_INVITES) and user registration (FEATURES_USER_REGISTRATION) are enabled. Zipline version through 3.7.9.Workaround: No fix is listed in the checked facts. Limiting the affected feature by disabling either FEATURES_INVITES or FEATURES_USER_REGISTRATION removes the condition the bug requires.
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-58405 (Zipline through 3.7.9 Invite Bypass via /api/auth/register 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-58405 (entry last updated 2026-11-13):
Affected:
- diced zipline: through 3.7.9
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Both invites (FEATURES_INVITES) and user registration (FEATURES_USER_REGISTRATION) are enabled. (source: https://www.vulncheck.com/advisories/zipline-through-3.7.9-invite-bypass-via-api-auth-register-endpoint)
- Zipline version through 3.7.9. (source: https://www.vulncheck.com/advisories/zipline-through-3.7.9-invite-bypass-via-api-auth-register-endpoint)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2024-58405 is not listed as of cve.now's last read.
This KEV status is for CVE-2024-58405 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-j2cw-9fvc-wr4r
- https://www.vulncheck.com/advisories/zipline-through-3.7.9-invite-bypass-via-api-auth-register-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-58405
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-58405"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- diced zipline
through 3.7.9
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-58405
Is CVE-2024-58405 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?
When both invites and user registration are enabled, registration succeeds without an invite. Unauthenticated users can create accounts through the /api/auth/register endpoint, view stats, and exhaust storage by uploading many files.Source: vulncheck.com
Which versions are affected by CVE-2024-58405?
zipline: through 3.7.9.Source: cve.now feed data
Am I affected, and how do I check?
Zipline through 3.7.9 with both FEATURES_INVITES and FEATURES_USER_REGISTRATION enabled. To check, look at the installed Zipline version and whether both settings are enabled in the configuration.Source: vulncheck.com
How do I fix CVE-2024-58405?
The checked facts name no fixed version or vendor patch, so no upgrade target can be given. Check the advisory for a fix before relying on any version.Source: vulncheck.com
What if there's no patch?
No fix is listed in the checked facts. Limiting the affected feature by disabling either FEATURES_INVITES or FEATURES_USER_REGISTRATION removes the condition the bug requires.Source: vulncheck.com