-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
trace function #1
Comments
Eric |
hi @eric-therond the program output : [[source_name] => [[0] => $testa_return], [source_line] => [[0] => 5], [source_column] => [[0] => 51], but I think maybe line 8 & line 9 should be added in the flow path,the source start in line 9:$var7 = $_GET["p"]; I debug the program,the code: |
thanks for the debug @tiandiyixian I will check, could you paste the source code of your analyzed file : E:\RCP\PHP\test.php ? Eric |
@eric-therond 2 function testa($param) |
The property taintedbyexpr of parameters of functions was not assigned to the expression of tainted argument of function during the function call (the flow was effectively broken here). I've corrected this, you could try now. Eric |
@eric-therond hi, I will test the project completely. after fixed the bug above, I tested some example,there is another bug, when I opened trace,the result was that: [[flow_name] => $this->object1, [flow_line] => 7, [flow_column] => 55, [flow_file] => E:\CP\PHP\tests\oop\simple19.php] source line was 15, sink line was 26,the trace was partly missing path,line 24 was the beginner, 269 if ($def_found->is_tainted()) |
It was the same mistake than previously, I've corrected this I have also added to the roadmap the handling of multiple flows for a same source (see for example : flow3.php), currently only one flow is traced (starting from $var1 is this example)) Eric |
thanks again,I will try it! |
hi,
Sir,I used the progpilot to analyze my php project ,It works well,but It seem that taint flow do not work,there is no taint trace info,only exits source and sink. Can you give me some suggestion?
The text was updated successfully, but these errors were encountered: