CVE-2024-8953
Composio 0.4.3
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2024-8953 is a critical-severity Dynamic Variable Evaluation (CWE-627) vulnerability in Composio Composio. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Reflective Code Loading (T1620); ranked in the top 37% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-8953 affects composiohq/composio version 0.4.3, where the mathematical_calculator endpoint improperly uses the unsafe eval() function to perform mathematical operations. This vulnerability, associated with CWE-627 (Dynamic Code Evaluation) and CWE-913 (Improper Control of Dynamically-Managed Code Resources), enables arbitrary code execution when untrusted input is passed to the eval() function. The issue has a CVSS v3.1 base score of 9.8, reflecting its critical severity due to high impacts on confidentiality, integrity, and availability.
The vulnerability is exploitable over the network with low attack complexity, requiring no privileges, no user interaction, and maintaining an unchanged scope. Remote attackers can send crafted input to the mathematical_calculator endpoint, triggering arbitrary code execution on the server hosting the affected composio instance. Successful exploitation grants attackers full control over the system, potentially leading to data theft, modification, or denial of service.
The primary advisory is available on Huntr at https://huntr.com/bounties/8203d721-e05f-4500-a5bc-c0bec980420c, which details the vulnerability report. Security practitioners should consult this reference for specific patch information or workarounds, as no additional mitigation details are provided in the CVE metadata. Upgrading to a fixed version of composiohq/composio beyond 0.4.3 is recommended to address the eval() misuse.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-6884
Vulnerability Data
In composiohq/composio version 0.4.3, the mathematical_calculator endpoint uses the unsafe eval() function to perform mathematical operations. This can lead to arbitrary code execution if untrusted input is passed to the eval() function.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 2 hardening rules · 2 OS baselines
—
Mitigating Controls (NIST 800-53 r5) AI
Access enforcement directly stops unauthorized reads/writes to dynamic code resources by applying authorization checks at access time.
Least privilege reduces the set of subjects that can reach or modify dynamic code resources, limiting the weakness's reach.
Input validation directly stops untrusted strings from being used as variable or function names in dynamic evaluation.
Secure engineering principles include avoiding or strictly controlling dynamic variable resolution from user input.
Isolating security functions from non-security code prevents unintended manipulation of dynamically managed executable resources.
Process isolation keeps each process's dynamic code resources in separate domains, blocking cross-process tampering.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices explicitly include controls that prevent improper handling of dynamic code resources.
Blocking unauthorized code execution directly limits the ability to abuse dynamically-managed resources.
Runtime-environment monitoring can detect exploitation of the weakness but does not prevent it.
Vulnerability identification can surface instances of CWE-913 but does not mitigate the root weakness.
Hardened configuration baselines can restrict dynamic code execution and variable access at runtime.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect dynamic evaluation flaws but does not prevent them by itself.
Secure development lifecycle mandates input validation and variable handling rules that reduce dynamic evaluation risks.
Application security requirements can specify restrictions on dynamic variable or function evaluation.
Secure architecture principles discourage unsafe dynamic evaluation constructs.
Secure coding standards directly prohibit or constrain dynamic variable evaluation to prevent arbitrary access.
Environment separation reduces exposure of dynamic code resources but does not address the underlying weakness.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Windows 10 (1 rule)
- V-220726 Data Execution Prevention (DEP) must be configured to at least OptOut. prevents CWE-913
Windows 11 (1 rule)
- V-253283 Data Execution Prevention (DEP) must be configured to at least OptOut. prevents CWE-913