neuroticnews25
Joined 1 year ago
Joined 1 year ago
I enjoyed reading it too, but the ending was disappointing. But not as dissapointing as most comments here.
Visiting https://superlogout.com/ logs you out of gmail with a cross-site GET request and it's not considered a vulnerability by google [0]
Posts could contain a safe subset of html (no scripting) including <img> as a feature - that used to be an acceptable design choice. In connection with the /signout it did allow for some unfortunate shenanigans - the kind of bug you just add additional sanitization for and move on, nothing indicative of a below average code quality.
>If you don't want to call that an XSS, what would you like to call that?
I would call the version you described a HTML injection to CSRF, but as Dylan16807 noted apparently it does fit OWASP's wide definition of XSS: "Since then, the term has widened to include injection of basically any content." [1] But that's not what happened, there was no HTML in usernames and HTML in posts was intended.
[0] https://bughunters.google.com/learn/invalid-reports/web-plat...
[1] https://cheatsheetseries.owasp.org/cheatsheets/Cross_Site_Sc...
Any examples?
My reading is the inability to understand serves only as an educational device for the reader. After all, at the end of the article the only point of contention is whether or not the objective truth exists. Is your point that the postmodern types don't claim that it doesn't? Or that they're an easy target used to later claim victory against a larger group?
EDIT typo
EDIT with every day I hate you more and more