CyberRota Analysis
AI-GeneratedThe vulnerability arises from improper input validation in the Ash framework, specifically in the handling of nested array attributes, which allows attackers to bypass constraints on the outer array, potentially leading to the acceptance of invalid data. This could result in data integrity issues, as inputs that violate defined constraints (like excessive elements or disallowed nil entries) can be persisted. Organizations using affected versions of the Ash framework, particularly those managing sensitive or critical data, should prioritize addressing this vulnerability to safeguard against potential exploitation.
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 Input Validation vulnerability in ash-project ash fails to enforce the outer array constraints on a doubly-nested {:array, {:array, type}} attribute, letting invalid input pass validation. Ash.Type.apply_constraints/3 (lib/ash/type/type.ex) handled the {:array, {:array, type}} case by mapping only the inner {:array, type} constraints over each element, so constraints declared on the outer array (such as min_length, max_length, and nil_items?) were never applied. An attacker could submit an outer list that violates those constraints (too many elements, or nil entries where disallowed) and have it accepted and persisted. The fix enforces the outer array constraints and adds explicit handling for nil and non-list inputs. This issue affects ash: from 2.16.1 before 3.32.2.