-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix MayUseToken vulnerability in AccountUpdates #1716
Closed
Closed
Changes from 3 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
b2a06fa
fix(account-update): validate that parentsOwnToken and inheritFromPar…
MartinMinkov 26dc9c2
feat(account-update.unit-test.ts): add unit tests for AccountUpdate.M…
MartinMinkov 32ba4cc
feat(changelog): prevent incorrect token inheritance handling in Acco…
MartinMinkov b3c972b
chore(bindings): update bindings submodule to 7263ff6f75e395c06ed1b67…
MartinMinkov df603bc
refactor(account-update.ts): simplify isParentsOwnToken and remove ch…
MartinMinkov 5a27a22
refactor(account-update.ts): move MayUseToken type and related functi…
MartinMinkov 6101789
fix(account-update.ts): add check for mayUseToken field in AccountUpd…
MartinMinkov bfc0735
Merge branch 'main' into audit/may-use-token
MartinMinkov ded6b4f
chore(bindings): update bindings submodule to 9c9c2051a
MartinMinkov c177ddf
fix(account-update.ts): remove provablePure from MayUseToken type def…
MartinMinkov File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there are a couple of issues with this
check()
method:MayUseToken
type when we witness it.type
:{ ...provablePure(...), check() { ... } }
MayUseToken.type
is not even the provable type that the auto-derived account update type will use -- it treats themayUseToken
property as an anonymous object of two bools, seegen/transactions.ts
andjs-layout.ts
. So, when witnessing entire account updates, nothing preventsmayUseToken
from having both props = trueAccountUpdate.witness()
with theskipCheck
parameter). From the finding, it wasn't clear to me if the OCamlmayUseToken
field really includes such a wellformedness check. If not, I think we should add it in the necessary places in o1js somehow, for example in the token contract where it walks child account updates.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Got it! Do these changes make sense then?
Constructing the check method properly and changing the AccountUpdate.check method to also check for mayUseToken?
EDIT: Had to add this change as well c177ddf
Doesn't seem to like my
check
method! https://github.com/o1-labs/o1js/actions/runs/9882602168/job/27295800852?pr=1716#step:4:201