I don't know the answer here but I did a perldoc -m MIME::Base64 and I see it's going through XS (at least on my machine). Now, of course C has no concept of tainting so when the C variable is copied from the tainted Perl variable and is then returned, it is returned as a copy of the C variable and returned without the tainted flag. (Is it called a flag?)
If my theory is right, I would think that lots of XS modules could have this issue.
In reply to Re: MIME::Base64 decode_base64 not tainted
by rowdog
in thread MIME::Base64 decode_base64 not tainted
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |