fix(escrow): assert caller authorization on refund and release (#299) - #480
Open
PINYOPATTANAWASANPORN wants to merge 4 commits into
Open
PINYOPATTANAWASANPORN wants to merge 4 commits into
PINYOPATTANAWASANPORN wants to merge 4 commits into
Conversation
…Fi#299) Ensure non-maintainer sponsors can only refund or release escrows attributed to themselves, preventing unauthorized cross-sponsor escrow cancellation or release.
…Fi#299) Ensure non-maintainer sponsors can only refund or release escrows attributed to themselves, preventing unauthorized cross-sponsor escrow cancellation or release.
…Fi#299) Ensure non-maintainer sponsors can only refund or release escrows attributed to themselves, preventing unauthorized cross-sponsor escrow cancellation or release.
…Fi#299) Ensure non-maintainer sponsors can only refund or release escrows attributed to themselves, preventing unauthorized cross-sponsor escrow cancellation or release.
|
@PINYOPATTANAWASANPORN is attempting to deploy a commit to the chonilius' projects Team on Vercel. A member of the Team first needs to authorize it. |
This branch has not been deployed
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary of Changes
Fixed an Authorization / Access Control vulnerability in
EscrowControllerandEscrowService(#299). Previously,refund(),release(), andsplitRelease()checked caller roles viaRolesGuard(@Roles(UserRole.MAINTAINER, UserRole.SPONSOR)), but did not thread the authenticated caller's identity intoEscrowServiceto verify resource ownership. This allowed any user with aSPONSORrole to callPOST /escrow/:id/refundorreleaseagainst another sponsor's locked escrow.This change threads the authenticated caller's
userIdintoEscrowServiceand introduces an explicit caller authorization check (assertCallerAuthorized) ensuring that non-maintainer sponsors can only refund or release escrows attributed to themselves (escrow.sponsorId === callingUserIdor matchingfundedByAddress).Root Cause / Technical Context
RolesGuardonly asserts that the request user possesses a required role (UserRole.SPONSOR/UserRole.MAINTAINER). It operates purely at the HTTP metadata level without entity context.EscrowService.refund(),release(), andsplitRelease()accepted onlyescrowIdwithout caller identity context. As a result, a validSPONSORaccount could trigger an unauthorized refund on anyLOCKEDescrow, forcing funds back to the funder and cancelling rival bounties or milestones in flight.req.user.userIdfromEscrowControllertoEscrowService.refund(),release(), andsplitRelease().assertCallerAuthorized(escrow, callingUserId, action)inEscrowService. Maintainers retain system-wide authority, while sponsors are restricted to their own attributed escrows.escrow.service.spec.tsvalidating authorized vs. unauthorized callers.Verification & Testing
Ran full NestJS Jest unit test suite for
src/escrow(5 test suites, 119 unit tests):