Repository navigation
reject on* attributes on AMP elements in validateAttributeChange - #40563
Open
madib06ops wants to merge 1 commit into
Open
madib06ops wants to merge 1 commit into
madib06ops wants to merge 1 commit into
Conversation
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
1 participant
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.
Purifier.validateAttributeChangeoverrides DOMPurify's rejection for anyamp-*element and then callsisValidAttrwithopt_purify=true, which skips theon*check on the assumption that DOMPurify already did it. amp-script'sSanitizerImpluses this to vet worker mutations, so worker code doingel = document.createElement('amp-img'); el.setAttribute('onclick', 'alert(document.domain)')gets a live inline handler on the main document, escaping the worker sandbox. Rejecton*attributes (other than AMP'son) in that override branch, the same ruleisValidAttrapplies when DOMPurify isn't involved; the new tests in test-purifier.js and test-amp-script.js fail without the change.