Elo: Code injection in Elo backends via unvalidated emission of programmatic AST fields

Summary

Elo is a purely functional expression language for no-code tools. Prior to 1.0.1, Elo's programmatic AST API accepts arbitrary values from JSON-deserialized input, plugin output, or other untyped sources and interpolates them into generated JavaScript, Ruby, Python, or SQL without runtime syntax validation. The affected fields are int_literal / float_literal .value, variable.name, member_access.property, object_literal keys, datapath segments, lambda.params[].name, and the SQL let binding name. Crafted values become executable expressions or identifiers, allowing arbitrary code execution in JavaScript, Ruby, and Python targets and SQL injection in the SQL target. This programmatic AST-object path is distinct from the plain-string constructor-chain sandbox escape. This issue is fixed in version 1.0.1.

Remediation

1. Inventory every enspirit elo deployment, including staging.
2. Upgrade enspirit elo to 1.0.1.
3. Confirm the running version after the upgrade.

References

• Advisoryhttps://github.com/advisories/GHSA-x9rp-7wh3-2rj5
• Referencehttps://github.com/enspirit/elo/security/advisories/GHSA-x9rp-7wh3-2rj5
• Referencehttps://github.com/enspirit/elo/commit/d2a89a8db76a244eb740687524a7e8529b7554b5
• Referencehttps://github.com/enspirit/elo/commit/fb57dd37a2669d9c412454225c5b89a2adba5d93