IN-SCOPE VULNERABILITIES

• Denial of service (DOS) vectors against the protocol (not against specific bundlers)
• Inconsistencies in assumptions, like situations where staked entities can be banned at a low cost to the attacker

SEVERITY

Critical:

EntryPoint bugs that can cause financial damage.

For example:

• Executing a call in an account without passing validation (or executing it more than once for a single validation).
• Stealing deposits or stakes.

High

On-chain griefing or censorship of an ERC-4337 compliant component.

For example:

• UserOps that would pass off-chain simulation but cause an entire bundle to revert on-chain.
• Ability to put a valid UserOp on-chain and get it to revert after validation - effectively censoring it.

Medium

Off-chain DoS vectors against the AA mempool, which are not solved by the ERC-7562 rules, and are unique to AA. i.e. not general libp2p attacks that would affect CL as well.

• Invalidating N UserOps at O(1) attack cost, effectively DoSing the entire mempool.
• Exploiting the staked reputation rules to censor a staked entity by getting it banned at O(1) attack cost (or O(n) if iteration cost is cheap enough).

Rationale for the severities:

• Critical - these would be a total failure of the system - user accounts could get drained. Equivalent to performing transactions on behalf of a user without the private key.
• High - these don't cause major financial loss, but hurt the core value of the system - censorship resistance. It may also lead to minor financial loss due to revert.
• Medium - these can temporarily disrupt the mempool and make it difficult to transact (similar to the Shanghai attacks). Can be fixed quickly without on-chain changes by fixing the rules and patching bundlers to use the fixed ones.

OUT-OF-SCOPE VULNERABILITIES

• Network-level DoS
• Attacks on any specific bundler, account or paymaster. Our bounties cover the contracts and the protocol definitions, not their implementations

Documentation: https://eips.ethereum.org/EIPS/eip-4337

• Make every effort not to damage or restrict the availability of products, services, or infrastructure
• Avoid compromising any personal data, interruption, or degradation of any service
• Don’t access or modify other user data, localize all tests to your accounts
• Perform testing only within the scope
• Don’t exploit any DoS/DDoS vulnerabilities, social engineering attacks, or spam
• In case you find chain vulnerabilities we’ll pay only for vulnerability with the highest severity.
• Don’t break any law and stay in the defined scope
• Any details of found vulnerabilities must not be communicated to anyone who is not a HackenProof Team or an authorized employee of this Company without appropriate permission
• In case that your finding is valid you might be asked for extra KYC verification to proceed with payments
• Perform testing on a private testnet wherever possible

For more information, check:

• ERC-4337 website

• Do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization
• No vulnerability disclosure, including partial is allowed for the moment.
• Please do NOT publish/discuss bugs

We are happy to thank everyone who submits valid reports which help us improve the security. However, only those that meet the following eligibility requirements may receive a monetary reward:

• You must be the first reporter of a vulnerability.
• The vulnerability must be a qualifying vulnerability
• Any vulnerability found must be reported no later than 24 hours after discovery and exclusively through hackenproof.com
• You must send a clear textual description of the report along with steps to reproduce the issue, include attachments such as screenshots or proof of concept code as necessary.
• You must not be a former or current employee of us or one of its contractor.
• ONLY USE YOUR HackenProof ADDRESS (in case of violation, no bounty can be awarded)
• Provide detailed but to-the point reproduction steps