You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(identity): bound fan-out on the audit-info collection path
GetAuditInfo in multisig and boolpolicy accounted for one level of
composite-identity nesting but never ran validateComponentIdentities, so
the component-count bound - and with it the duplicate and none-component
checks - applied to verifier deserialization and matcher construction but
not to audit-info collection.
The depth bound does not cover that case: a single level fanning out to
thousands of components is one recursive step that resolves one audit-info
lookup per component, and descends again for any composite component. A
20 KB multisig identity with 10,000 components drove 10,001 provider
lookups with the component bound configured at 4. The path is reachable
from remote input during recipient registration.
Route both through the same choke point the other chains use, and cover
the chain in the nesting tests for depth and for fan-out at limit and
limit+1.
Signed-off-by: AkramBitar <akram@il.ibm.com>
0 commit comments