Asteval
Monthly
Sandbox escape in asteval (the lmfit restricted Python expression evaluator) before 1.0.9 lets an attacker-controlled expression turn numpy's ndarray.ctypes wrapper into an arbitrary process-memory read/write primitive, which is equivalent to code execution and can also leak secrets or crash the host process. Exploitation requires the DEFAULT Interpreter with numpy enabled (the default whenever numpy is installed) and a host application that evaluates untrusted expression strings; per the assessed vector it is unauthenticated (PR:N) with no user interaction and needs no import, __dunder__ access, eval, or getattr. The headline is a sharp signal conflict: NVD-style scoring gives only 5.5 (AV:L/AC:L/PR:N/UI:R, availability-only), while the independent assessment scores the same flaw CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H, so real-world risk depends entirely on how the consuming application exposes the evaluator. No public exploit code was identified at time of analysis, and the issue is fully remediated by upgrading to 1.0.9.
Sandbox escape in asteval (the lmfit restricted Python expression evaluator) before 1.0.9 lets an attacker-controlled expression turn numpy's ndarray.ctypes wrapper into an arbitrary process-memory read/write primitive, which is equivalent to code execution and can also leak secrets or crash the host process. Exploitation requires the DEFAULT Interpreter with numpy enabled (the default whenever numpy is installed) and a host application that evaluates untrusted expression strings; per the assessed vector it is unauthenticated (PR:N) with no user interaction and needs no import, __dunder__ access, eval, or getattr. The headline is a sharp signal conflict: NVD-style scoring gives only 5.5 (AV:L/AC:L/PR:N/UI:R, availability-only), while the independent assessment scores the same flaw CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H, so real-world risk depends entirely on how the consuming application exposes the evaluator. No public exploit code was identified at time of analysis, and the issue is fully remediated by upgrading to 1.0.9.