sig collision?
Open
- Dominant language
- Solidity
- Stars
- 24
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
Looks like ANY trick is fine for src/dest, but is there some fuckery that could happen with a malicious function signature `bytes4(uint32(-1))`? @dbrock
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing how src/dest and the 4-byte function signature are encoded and compared. Check the behavior of bytes4(uint32(-1)) and document whether a malicious signature can collide; done means a confirmed result with the relevant security implications recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- solidity
- Domain
- authorization, blockchain, security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100