Though, really, is that interesting? Yes, you should treat all input data as data no matter where it came from. And you should have checks in place to reject any data that is out of size/whatever constraints for your software.

And for the love of secure software, never blindly execute code from a serialized source without damned good reasons for thinking that source is safe.

>Though, really, is that interesting?

Yes. Trusting human DNA is something that WILL absolutely, 100%, no-doubt-about it happen in the future and you will hear about it. People are good at finding ways to screw things up.

Sorry, the interesting like there was supposed to refer to the advice of always sanitize inputs. That, by itself is interesting.

Exploring ways it can hurt you in DNA? Yeah, fun thought experiment.

I remember that perl has (had?) a feature where all variables would be "tainted". Using a tainted variable would make the program exit in an error and the only way to clean them is to pass them through a regex.

Tainted is a terribly flawed concept unfortunately. At least the way it's implemented normally.

Strings are never universally tainted. They're tainted for a specific purpose. One language will treat backticks as a string quote, another as a subshell substitution. One will think $ is ok, another will interpolate the string. But in most cases I've seen, tainted flag is just used for "Ah, we quoted the ' in the string - you're safe now" :-(