GHSA-8x4m-qw58-3pcx: mppx has multiple payment bypass and griefing vulnerabilities
Multiple vulnerabilities were discovered in tempo/charge and tempo/session which allowed for undesirable behaviors, including:
- Replaying
tempo/chargetransaction hashes across push/pull modes, across charge/session endpoints, and via concurrent requests - Performing free
tempo/chargerequests due to missing transfer log verification in pull-mode - Replaying
tempo/chargecredentials across routes via cross-route scope confusion (memo/splitsnot included in scope binding) - Manipulating the fee payer of a
tempo/chargehandler into paying for requests (missing sender signature before co-signing) - Bypassing
tempo/sessionvoucher signature verification - Piggybacking off existing
tempo/sessionchannels via settle voucher reuse and weak channel ID binding - Performing free
tempo/sessionrequests by exploiting channel reopen without on-chain settled state - Accepting deductions on finalized
tempo/sessionchannels - Bypassing payment on free routes via method-mismatch fallback
- Griefing
tempo/sessionchannels via force-close detection bypass (closeRequestedAtnot persisted)
References
Code Behaviors & Features
Detect and mitigate GHSA-8x4m-qw58-3pcx with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →