CyberRota Analysis
AI-GeneratedA vulnerability in the ash-project's ash_lua allows unauthorized Lua scripts to access sensitive attributes not included in the exposed-field allow-list, potentially exposing private data such as hashed passwords. This issue arises from improper validation of field access in the Lua runtime, enabling any user capable of submitting or influencing a Lua script to exploit this flaw. Organizations using ash_lua versions from 0.1.0 to before 0.2.1 should prioritize patching this vulnerability to mitigate the risk of data exposure.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Improper Protection of Alternate Path vulnerability in ash-project ash_lua allows a user-supplied Lua script to read attributes that are not on the exposed-field allow-list. AshLua exposes Ash resources to Lua scripts, gated by a manifest declaring which fields are exposed. The read action's operation aggregate path in AshLua.Runtime took the field name straight from the Lua call and resolved it with only String.to_existing_atom and Ash.Query.Aggregate.new!, neither of which consults the exposed-field allow-list the normal fields path enforces. A script can therefore read the value of any attribute of any record the actor may read, including private sensitive?: true columns, via resource.read({ operation = {"list", "hashed_password"} }); min and max give a value oracle. Anyone able to submit or influence a Lua script can reach this. This issue affects ash_lua: from 0.1.0 before 0.2.1.