dbcve.org
Infinite LoopWeakness · CWE-835

CVE-2024-10821

HIGH · 7.5 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 →
84/100
Remediation priority · High
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
A Denial of Service (DoS) vulnerability in the multipart request boundary processing mechanism of the Invoke-AI server (version v5.0.1) allows unauthenticated attackers to cause excessive resource consumption. The server fails to handle excessive characters appended to the end of multipart boundaries, leading to an infinite loop and a complete denial of service for all users. The affected endpoint is `/api/v1/images/upload`.

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 · moderate confidence

The vulnerability exists in Invoke-AI v5.0.1's multipart request parser at the /api/v1/images/upload endpoint. When an attacker sends multipart requests with excessively long characters appended to the boundary delimiter, the parser enters an infinite loop due to improper boundary length handling, exhausting server resources and causing DoS for all users.

MitigationApply vendor patches when available; as a compensating control, implement request size limits and boundary length validation at a reverse proxy or WAF level to reject malformed multipart requests before they reach the application.

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Identify Invoke-AI installation version
    Check the installed Invoke-AI version via package manager (pip show invoke-ai) or check the version file in the installation directory
    Affected if Version is v5.0.1 specifically
  2. Verify /api/v1/images/upload endpoint is exposed
    Review web server or application configuration to confirm the /api/v1/images/upload endpoint is accessible (check reverse proxy, API gateway, or direct service exposure)
    Affected if The endpoint is exposed and reachable from the network
  3. Confirm multipart file upload feature is enabled
    Check Invoke-AI configuration files for upload/enable_multipart or related settings that control whether image upload via multipart requests is permitted
    Affected if Multipart upload feature is enabled in configuration
  4. Check for boundary length validation
    Inspect the application or upstream proxy/WAF configuration for any Content-Type boundary length limits or validation rules
    Affected if No boundary length validation or size limits are configured for multipart requests

A user is affected if they are running Invoke-AI v5.0.1 with the /api/v1/images/upload endpoint exposed and multipart upload enabled without boundary length validation in place.

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

Apply vendor patches when available; as a compensating control, implement request size limits and boundary length validation at a reverse proxy or WAF level to reject malformed multipart requests before they reach the application.

Recommended fix Moderate confidence

Latest stable Invoke-AI release (check GitHub releases for v5.0.2 or later)

  1. 1. Check the official Invoke-AI GitHub repository (github.com/invoke-ai/InvokeAI) for the latest stable release
  2. 2. Identify a version newer than v5.0.1 that contains the security fix for CVE-2024-10821
  3. 3. Before upgrading, backup any existing models, configurations, and user data
  4. 4. Stop the Invoke-AI server to prevent partial updates
  5. 5. Upgrade Invoke-AI by following the official installation guide for your deployment method (pip, Docker, or source)
  6. 6. Verify the new version number matches the expected fixed release
  7. 7. Restart the Invoke-AI server and confirm the `/api/v1/images/upload` endpoint accepts legitimate multipart uploads
  8. 8. Test that the server no longer enters an infinite loop when processing malformed boundaries with excessive characters
Caveat Minor version upgrades in Invoke-AI typically include new features and model support; review release notes for any breaking changes to workflows or 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
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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