NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
sprint formats inputs and taint (Score:1)
qx{ sprintf "blah %s blah", $input }without taint checking the$inputfirst is not safe, never was, never should have been considered safe. If someone ever said "it's only a way to crash the program, no way to break in here", they were not listening to history. Running system commands with user input is always going to be a target of opportunity, you have to defend that in depth. You've got to check for buffer overrun (even if you can't see the buffer ) andBill
# I had a sig when sigs were cool
use Sig;
Re: (Score:1)
I think what’s happening is that they’re doing something like this:
where
$precisionderives from user input. This exposes Perl code to all the same format string vulnerabilities [wikipedia.org] that have commonly been found in C code. I’ve been pointing this out for a while now. I’m surprised that not more people have picked up on it.The right way to write that code, in the general case, is like so:
Re: (Score:2)
So I assume that you have long since reported this through perlbug and/or perl5-porters and since it's a security flaw also contacted the branch maintainers (Rafael and Nicholas) directly?
Re: (Score:1)
I think what he is saying is that it isn't a *core* Perl flaw but a flaw in programming methodology.
Reply to This
Parent
Core perl or methodology? (Score:1)
Bill
# I had a sig when sigs were cool
use Sig;