You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem: Currently the default ruleset includes many of the common keywords/commands that can be used to trigger an RCE attack, e.g. system, eval, exec, and qx. However, it does not provide a solution for executing a system command using the backtick syntax, e.g.
my $cmd = "ls -a $folder" # assume $folder is dynamic/user provided value; if unchecked, could result in RCE attack
my @results = `$cmd`
Is there a way to write a rule or add functionality to allow for zarn to identify and flag this kind of code?
The text was updated successfully, but these errors were encountered:
At the moment, ZARN looks just for "risks functions" and then checks if some payload can be used to perform an attack. So, in the current structure we cannot create any rules for this use case of Backticks =/ (I'm trying to put more functionality into ZARN and will consider this use case.)
I don't know much about Perl::Critic but it also has some security checks, is it covered for this case?
@htrgouvea Perl::Critic was not able to flag this issue either, in fact it misses many of the issues your tool identifies. If this is something that could be considered for addition that would be awesome! Your tool is very useful and your efforts much appreciated.
Problem: Currently the default ruleset includes many of the common keywords/commands that can be used to trigger an RCE attack, e.g.
system
,eval
,exec
, andqx
. However, it does not provide a solution for executing a system command using the backtick syntax, e.g.Is there a way to write a rule or add functionality to allow for zarn to identify and flag this kind of code?
The text was updated successfully, but these errors were encountered: