-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
fix: DOM Clobbering CVE #22688
Open
Sec-ant
wants to merge
1
commit into
emscripten-core:main
Choose a base branch
from
Sec-ant:security/dom-clobbering-cve
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
fix: DOM Clobbering CVE #22688
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,11 +1,13 @@ | ||
section size addr | ||
TYPE 51 10 | ||
IMPORT 31 63 | ||
FUNCTION 14 96 | ||
GLOBAL 9 112 | ||
EXPORT 9 123 | ||
ELEM 9 134 | ||
CODE 1556 146 | ||
DATA 77 1704 | ||
JS 6756 0 | ||
Total 8512 | ||
TYPE 41 10 | ||
IMPORT 7 53 | ||
FUNCTION 9 62 | ||
TABLE 5 73 | ||
MEMORY 6 80 | ||
GLOBAL 8 88 | ||
EXPORT 17 98 | ||
ELEM 9 117 | ||
CODE 1083 129 | ||
DATA 72 1214 | ||
JS 4799 0 | ||
Total 6056 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Its nice to see the progress we've made on overall code size here since this test was last rebaselined |
Binary file not shown.
This file contains 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Man.. this is kind of ugly, and seems like it will increase code size.
I'm not necessarily against landing this, but I wonder if we can further limit the cases where
_scriptName
is used.. maybe we can even eliminate it somehow.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is pretty ugly :/ I wonder if the
.toUpperCase()
part at least is not needed? When testing, I am getting all uppercase letters in.tagName
already. Is there a known browser where tagName not in upper case, or why is the.toUpperCase()
there?I think I would write a function into parseTools.mjs:
and then in all these places that read
document.currentScript.src
, doThis way we have clean JS code and a way to evolve out of this awkwardness for users in the future.