You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, DOMPurify protects itself against DOM Clobbering. But the resulting markup itself still has clobbering potential when being used by the sanitizing website.
Should be by default prevent that? My thought would be: If an element's name is at the same time a property in document, the element should be removed. What do you think? We would prevent XSS and DOM clobbering.
Sounds good to me! The only downside is that sanitize() wouldn’t be a pure/deterministic function anymore… But that doesn’t really matter. Improved security is more important.
Right now, DOMPurify protects itself against DOM Clobbering. But the resulting markup itself still has clobbering potential when being used by the sanitizing website.
Should be by default prevent that? My thought would be: If an element's name is at the same time a property in
document
, the element should be removed. What do you think? We would prevent XSS and DOM clobbering.//cc @fhemberger @mathiasbynens
The text was updated successfully, but these errors were encountered: