Timeline for Appending string to a user input can stop xss in jquery selector?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 25 at 11:23 | comment | added | niopiop poiu | @Sjoerd the only thing from the link you mentioned is timing attack , is it the only possibility ? | |
| Aug 25 at 11:19 | comment | added | niopiop poiu |
@Ja1024 It takes the user input into a variable and then do as @Sjoerd said : $('.somethingX ' + userinput) which make it not possible to close the selector and you will get the same error .
|
|
| Aug 25 at 11:11 | comment | added | Sjoerd |
@Ja1024 I interpreted the injection as client-side script running $('.somethingX ' + userinput).
|
|
| Aug 25 at 11:09 | comment | added | Sjoerd | See also Is XSS possible with jQuery(location.hash)? | |
| Aug 25 at 2:57 | comment | added | Ja1024 |
When you can inject input into a jquery selector, you already are in a JavaScript context. What prevents you from simply writing JavaScript code directly instead of trying to use the HTML document to trigger the code? Let's say the vulnerable code is $('.foo<input here>').bar();. Why not use $('.foo'); alert('XSS'); //').bar();? If there's some specific restriction which prevents this, then you need to mention that in your question.
|
|
| Aug 25 at 1:14 | history | asked | niopiop poiu | CC BY-SA 4.0 |