Skip to content
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

imp: disallow submessage execution #4130

Merged

Conversation

crodriguezvega
Copy link
Contributor

Description

Item 4.4 of Confio's report of 08-wasm audit.

This check prevents Wasm light client contracts to execute sub messages.

closes: #XXXX

Commit Message / Changelog Entry

type: commit message

see the guidelines for commit messages. (view raw markdown for examples)


Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

  • Targeted PR against correct branch (see CONTRIBUTING.md).
  • Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
  • Code follows the module structure standards and Go style guide.
  • Wrote unit and integration tests.
  • Updated relevant documentation (docs/) or specification (x/<module>/spec/).
  • Added relevant godoc comments.
  • Provide a commit message to be used for the changelog entry in the PR description for review.
  • Re-reviewed Files changed in the Github PR explorer.
  • Review Codecov Report in the comment section below once CI passes.

@@ -261,5 +261,8 @@ func call[T ContractResult](ctx sdk.Context, clientStore sdk.KVStore, cs *Client
if !output.Validate() {
return output, errorsmod.Wrapf(errors.New(output.Error()), "error occurred while calling contract with code ID %s", hex.EncodeToString(cs.CodeId))
}
if len(out.Messages) > 0 {
return output, errorsmod.Wrapf(ErrWasmSubMessagesNotAllowed, "code hash (%s)", hex.EncodeToString(cs.CodeId))
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I mention code hash in the message, assuming that this PR will eventually get merged.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The var naming of out doesn't really feel intuitive to me, but we can rename it to whatever later, also maybe we could add something like this in a future improvement - handleContractResponse() ref

@crodriguezvega crodriguezvega changed the title disallow submessage execution imp: disallow submessage execution Jul 19, 2023
Copy link
Contributor

@DimitrisJim DimitrisJim left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good to go after #4091

Copy link
Contributor

@damiannolan damiannolan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@@ -261,5 +261,8 @@ func call[T ContractResult](ctx sdk.Context, clientStore sdk.KVStore, cs *Client
if !output.Validate() {
return output, errorsmod.Wrapf(errors.New(output.Error()), "error occurred while calling contract with code ID %s", hex.EncodeToString(cs.CodeId))
}
if len(out.Messages) > 0 {
return output, errorsmod.Wrapf(ErrWasmSubMessagesNotAllowed, "code hash (%s)", hex.EncodeToString(cs.CodeId))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The var naming of out doesn't really feel intuitive to me, but we can rename it to whatever later, also maybe we could add something like this in a future improvement - handleContractResponse() ref

@crodriguezvega crodriguezvega merged commit 62ed4fb into feat/wasm-clients Jul 20, 2023
@crodriguezvega crodriguezvega deleted the carlos/disallow-submessage-execution branch July 20, 2023 19:11
@faddat faddat mentioned this pull request Sep 10, 2023
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants