
PEACH
Un cadre d’isolation des locataires
twzrd-x402-gate 0.23.0 and earlier
PAYMENT-REQUIRED header is not canonical base64 skipped every check (critical). createTwzrdPolicyFetch and createTwzrdPayingFetch read the header with a strict base64 reader. When that reader refused the text (missing = padding, or unused low bits set), both treated the 402 as having nothing to check and handed it to the payer. The x402 client decodes the same text with atob, which accepts it, and signs. A seller that strips the padding from its own header was paid with no wash check, no policy check (blocklist, allowlist, per-call and cumulative ceilings, new-counterparty cap) and no ledger line. The attacker only needs to be the seller. The x402 client's own default limit still applies unless the application turned it off. The hook entry points, createBuyerFetch, createGuardedX402Fetch and twzrd.safeFetch refuse such a header and are not affected.createTwzrdPolicyFetch counted a payment only when the paid response was 2xx (high). A seller that took the signed payment and answered an error, another 402, or closed the connection was never counted against dailyCeilingUsd, a mandate's monthly ceiling or newCounterpartyCap.newCounterpartyCap.newCounterpartyCap counted each spelling separately.auth-capture offers and Solana upto offers were scored as an exact payment to payTo (medium). Both schemes can pay parties named in extra. The Base Worker approval never read the scheme.requireOfferBinding this release also refuses a plain token-account Create, a create not funded by the fee payer, a message version other than legacy or v0, and an offer that sets extra.memo.
@twzrd1111/agent-killswitch 0.4.0 and earlierusage block could not be priced settled at $0 (medium). Fractional, missing or non-numeric token counts were read as 0, so such a response never counted against the hour or day limit.ENOTFOUND as never sent, which releases a hold after a billed call (documentation).close or topUp credential sent together with an x402 payment header skipped the budget hold (low).twzrd-x402-gate 0.24.0@twzrd1111/agent-killswitch 0.5.0
0.24.0 turns allows into refusals. The refusal codes are in the package CHANGELOG.md, and COMPATIBILITY.md lists what changes for a caller.For item 1 of the gate: use createBuyerFetch, createGuardedX402Fetch, the client hook or twzrd.safeFetch, which refuse a header they cannot read, and keep the x402 client's default spend limit on. There is no workaround for the other items; upgrade.
twzrd-mcp-server 0.6.3 and @wzrd_sol/eliza-plugin 0.10.2 depend on twzrd-x402-gate 0.20.2. Releases of both on the patched gate will follow.
Source: NVD
Évaluation gratuite des vulnérabilités
Évaluez vos pratiques de sécurité cloud dans 9 domaines de sécurité afin d’évaluer votre niveau de risque et d’identifier les lacunes dans vos défenses.
Obtenez une démo personnalisée
"La meilleure expérience utilisateur que j’ai jamais vue, offre une visibilité totale sur les workloads cloud."
"Wiz fournit une interface unique pour voir ce qui se passe dans nos environnements cloud."
"Nous savons que si Wiz identifie quelque chose comme critique, c’est qu’il l’est réellement."