News for hackers. Stuff that matters.
Re:GetElementById vs. QuerySelector by ducharmdev on Thursday November 25, 2021 @11:54PM (#29347574)
Woah, no way. Although I could see this being abused, it's amazing that this even works.
Re:GetElementById vs. QuerySelector by esnard on Friday November 26, 2021 @04:11AM (#29348584)
It has been abused to allow remote code execution in LastPass, a password manager.

https://bugs.chromium.org/p/project-zero/issues/detail?id=12...

Re:GetElementById vs. QuerySelector by JimDabell on Friday November 26, 2021 @10:34AM (#29351101)
You could also crash Internet Explorer 6 simply by including an element with id="tags" on the page. When the user chose to print the page out, the browser would try to access window.tags, find the element instead of what it was expecting to find, and give up.
Re:GetElementById vs. QuerySelector by flomo on Friday November 26, 2021 @02:35AM (#29348163)
This was the standard way of DOM touching in the early days, e.g.

  FormName.FieldName.value = "foo";
Re:GetElementById vs. QuerySelector by vgallur on Friday November 26, 2021 @06:18AM (#29349194)
There are XSS attacks abusing this behaviour named DOM Clobbering

https://portswigger.net/research/dom-clobbering-strikes-back