-
Notifications
You must be signed in to change notification settings - Fork 212
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
Zoe is gullible to issuer's allegation of brand #1378
Comments
erights
added
bug
Something isn't working
ERTP
package: ERTP
security
Zoe
package: Zoe
zoe-alpha-release
labels
Aug 5, 2020
Yup, this is indeed a vulnerability. We use the issuerTable in a couple of places: the Zoe Service, the Contract Facet, and the wallet. We should check each of these places. I think the Zoe redesign PR is an appropriate place for this change. |
Yes, that looks good. |
Fixed in agoric-sdk in #1414 but we should remain aware of this issue. |
Merged
Closed in #1443 |
This was referenced Jan 17, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
agoric-sdk/packages/zoe/src/state.js
Line 208 in d9bc9ec
together with
agoric-sdk/packages/zoe/src/state.js
Lines 229 to 231 in d9bc9ec
enters a binding from the brand that the issuer alleges to an issuer record which includes the issuer. But a malicious issuer could report someone else's brand, disrupting Zoe's possible later attempt to register the true issuer of that brand. We just need to also check
brand.isMyIssuer(issuer)
to ensure they are mutually acceptable to each other. The pair may still misbehave, but they can't interfere with a later attempt to register the true owner of that brand.There may be similar vulnerabilities elsewhere we ask an issuer for its brand without asking the brand's opinion.
The text was updated successfully, but these errors were encountered: