Three Policy Gaps That Let Session Keys Exceed Their Permissions
Session keys and agent wallets are meant to act within tightly scoped limits, but their policy code often contains flaws that undermine those limits. One common gap is that spending policies count only transfers, so an approval call can grant an attacker a lasting claim on funds that survives revocation of the session. Allowlists keyed on contract addresses are another weak point, since allowing a contract exposes every function on it, including dangerous generic execution or admin methods. Fixed-window spending caps can also be exploited at window boundaries, allowing roughly double the intended amount in a short span, a risk amplified by automated agents that retry rapidly.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in