Skip to content

chore: document some edge case scenarios#188

Open
MoMannn wants to merge 1 commit into
mainfrom
chore--update-docs-with-edge-cases
Open

chore: document some edge case scenarios#188
MoMannn wants to merge 1 commit into
mainfrom
chore--update-docs-with-edge-cases

Conversation

@MoMannn

@MoMannn MoMannn commented Jun 11, 2026

Copy link
Copy Markdown
Member

What?

  • Document some edge case security scenarios.

Why?

How?


Note

Low Risk
Markdown-only documentation updates with no changes to contracts or execution paths.

Overview
Adds documentation-only security guidance for caveat enforcer edge cases—no contract or runtime behavior changes.

CaveatEnforcers.md now briefly describes AllowedTargetsEnforcer / AllowedMethodsEnforcer (outer-call guards only) and ERC20PeriodTransferEnforcer, each with a warning and a link into Security.md.

Security.md gains a Caveat Enforcer Combination Risks section covering two scenarios: allowing redeemDelegations via AllowedMethodsEnforcer on a self-targeted delegation (nested calldata not checked → apparent narrow permission can become arbitrary execution), and attaching multiple ERC20PeriodTransferEnforcer caveats to one delegation (shared (delegationManager, delegationHash) state → only the first initializer’s terms apply).

Reviewed by Cursor Bugbot for commit e4126b8. Bugbot is set up for automated code reviews on this repo. Configure here.

@MoMannn MoMannn requested a review from a team as a code owner June 11, 2026 08:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant