dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-21552

CRITICAL · 9.8 CVSS v3.1 Published 2024-07-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
All versions of `SuperAGI` are vulnerable to Arbitrary Code Execution due to unsafe use of the ‘eval’ function. An attacker could induce the LLM output to exploit this vulnerability and gain arbitrary code execution on the SuperAGI application server.

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

SuperAGI contains an Arbitrary Code Execution vulnerability in all versions due to unsafe use of the Python eval() function. An attacker can craft malicious inputs that are processed by the LLM and subsequently evaluated by eval(), allowing execution of arbitrary OS commands on the server.

MitigationReplace all instances of eval() with safe alternatives such as ast.literal_eval() for literal evaluation, or implement a sandboxed execution environment; additionally implement input validation on LLM outputs before any evaluation occurs.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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. Identify SuperAGI installation and version
    Run 'pip show superagi' or locate the SuperAGI source directory and check the version (e.g., version file or __version__)
    Affected if SuperAGI is present (all versions are affected)
  2. Search for unsafe eval() usage in source code
    Use 'grep -r "eval(" <SuperAGI_path>' to locate any eval() calls in the Python source files
    Affected if Any eval( call is present in the codebase
  3. Confirm LLM integration is enabled
    Inspect the configuration files for LLM provider settings and verify that the LLM input pipeline is active
    Affected if LLM is configured and user prompts can reach the backend
  4. Verify whether LLM outputs are validated before eval()
    Search for any sanitization, AST parsing, or sandboxing code that processes LLM responses before eval() (e.g., grep for 'ast.literal_eval' or 'safe')
    Affected if No validation or sandboxing is found between LLM output and eval()

If SuperAGI is installed, contains eval() calls, has an active LLM integration, and lacks input validation on LLM outputs before eval(), the environment is vulnerable to CVE-2024-21552.

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

Replace all instances of eval() with safe alternatives such as ast.literal_eval() for literal evaluation, or implement a sandboxed execution environment; additionally implement input validation on LLM outputs before any evaluation occurs.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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