a2ui-project a2ui Resource Exhaustion Vulnerabilities

Unbounded recursion in the a2ui web_core v0_9 renderer (DataContext.resolveSignal / resolveDynamicValue) lets a remote attacker who can supply A2UI dynamic-value or function-call expression trees crash or hang the rendering context through call-stack exhaustion, an availability-only denial of service. All versions listed through 0.10.6 (EUVD enumerates 0.10.0 through 0.10.6) are affected; the CVSS 4.0 score is 6.9 with VA:L only, and the project's own assessed vector (CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L) confirms no confidentiality or integrity impact and no authentication or user interaction requirement. A public PoC reference exists in issue #2388; it is not verified as working exploit code, and there is no KEV listing, so this is a moderate, availability-only issue rather than a top-tier emergency, prioritized as 'this_month' by vuln.today. A vendor fix is available as PR #2432 / commit c76e17272e52c12c6dcf68905b1df978c39e9aa5, which introduces a MAX_DYNAMIC_VALUE_DEPTH guard of 1000.

a2ui 0.10.0 through 0.10.6 leaks stack traces and internal file-system paths through expression-error messages: the web_core renderer's DataContext.dispatchExpressionError copied the raw V8 'e.stack' into the 'details' field of the dispatched error instead of returning only a sanitized message. An attacker who can make expression evaluation throw (for example a dynamic value calling formatNumber with an out-of-range 'decimals' argument that raises a RangeError) can read the returned stack detail remotely; the CVSS 4.0 score is 2.1 (assessed CVSS 3.1: AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N), so confidentiality of internal error detail is the only impact, with low-privileged authenticated access required. A public PoC reference exists in issue #2385 but is not verified as working exploit code, no CISA KEV entry indicates active exploitation, and the vendor patch is available in commit 8f149a1c7b0ce1fa8e93ac3adfa5fda960faeb01.

Unbounded array-index handling in a2ui's web_core v0.9 state module (DataModel.set, renderers/web_core/src/v0_9/state/data-model.ts) in versions up to and including 0.10.6 allows a low-privileged caller who can submit a data-model path to force array auto-vivification or an array clone at an enormous index - for example '/items/999999999' or '/newArray/10000000/field' - exhausting renderer memory or hanging the thread. The assessed impact is availability-only against the client-side renderer (CVSS 3.1 AV:N/AC:L/PR:L/UI:N/C:N/I:N/A:L; vendor scoring 2.1), with no confidentiality or integrity effect and no server-side compromise. A public PoC reference exists (issue #2386); it is not verified as working exploit code, no KEV-listed active exploitation is reported, and priority is monitor. An upstream fix is available as PR #2430 / commit 82789191ce551f4d7a095d273773fb24bd764c9d, which caps array indices at 10000.

Resource exhaustion in a2ui Web Core versions 0.10.0 through 0.10.6 lets low-privileged remote callers degrade availability by passing excessive or unknown function-call arguments to the data-context Resolver. The resolver in renderers/web_core/src/v0_9/rendering/data-context.ts did not validate argument names or enforce a maximum argument count before PR #2417, which adds MAX_FUNCTION_CALL_ARGS and rejects unknown keys. A public PoC reference exists; it is not verified as working exploit code. No active exploitation is confirmed in the supplied intelligence, and the assigned priority is monitor.

Unbounded resource consumption in the a2ui web_core renderer (versions 0.10.0 through 0.10.6) lets an attacker who can influence a data-bound dynamic ChildList force the client to materialize an arbitrarily large number of child nodes. The flaw sits in the GenericBinder path of renderers/web_core/src/v0_9/rendering/generic-binder.ts, which pre-patch applied no size cap when expanding a {componentId, path} children binding into one node per array element; a 12,000-element array produced 12,000 nodes in the reference test. Exploitation requires write access to the bound data model (authenticated, PR:L per the assessed vector), causes only low availability degradation of the browser-side renderer with no confidentiality or integrity impact, and a public PoC reference exists on the upstream issue tracker although it is not verified as working exploit code. Priority signals are uniformly low (vuln.today decision: monitor), so this is a hardening item rather than an urgent patch.

Resource exhaustion in the a2ui web renderer's expression parser affects versions 0.10.0 through 0.10.6: a crafted template string handed to the formatString basic function is parsed without any bound on length or part count, so an attacker who can supply that input can force excessive parsing work in a victim's renderer. The CVSS 4.0 vector requires low privileges (PR:L) and passive user interaction (UI:P) - a victim must load or render the malicious expression - and the resulting impact is limited to availability (VA:L) with no confidentiality or integrity effect. A public PoC reference exists (GitHub issue #2389); it is not verified as working exploit code, there is no CISA KEV listing, and the priority decision is 'this_month' rather than an emergency.