Re:UK Company named "><SCRIPT SRC=HTTPS://MJT.XSS.HT> LTD" f...
by drdaeman on Friday October 25, 2024 @05:41PM
(#41950083)
As I get it, inputs aren’t an issue, failure to correctly escape outputs to match the target format is.
[ Parent
| on HN ]
Re:UK Company named "><SCRIPT SRC=HTTPS://MJT.XSS.HT> LTD" f...
by paulryanrogers on Friday October 25, 2024 @06:02PM
(#41950249)
Good point, both are needed: secure parsing and secure rendering.
Re:UK Company named "><SCRIPT SRC=HTTPS://MJT.XSS.HT> LTD" f...
by hnick on Friday October 25, 2024 @09:09PM
(#41951662)
I liked perl's taint mode. It seemed pretty good against the "oops, forgot to sanitise this and you used it as output" situation that probably accounts for a lot of these issues. It won't force you to correctly sanitise, but assuming you have that capability it lets you know about gaps so you can plug them.