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
Pre-submission checklist
[x] I've checked the list of common issues and mine does not appear
Bug description
Please consider the following program source code
classMyClass:
defmy_function(self):
self.function1("", "", self.source()) # NOT reported by pysaself.sink(self.source()) # Correctly reported by pysadeffunction1(self, arg1: str, arg2: str, arg3: str):
foriinrange(10):
arg0=arg1self.sink(arg3) # NOT reported by pysaarg1=arg2arg2=self.function2(arg1)
deffunction2(self, arg0: str):
returnarg0defsource(self):
return"Secret"defsink(self, param: str):
pass
The call to sink in function1 is not detected by pysa, and all the statements around it seem to be responsible. If we for example remove one of the unnecessary assignments, replace the call to function2 with just another assignment or move all the statements out of the loop, pysa correctly reports the taint leak.
In my sources_sinks.pysa I declare source and sink as taint sources and sinks respectively (this config works as we can see with the detected leak in my_function):
Pysa Bug
Pre-submission checklist
[x] I've checked the list of common issues and mine does not appear
Bug description
Please consider the following program source code
The call to
sink
infunction1
is not detected by pysa, and all the statements around it seem to be responsible. If we for example remove one of the unnecessary assignments, replace the call tofunction2
with just another assignment or move all the statements out of the loop, pysa correctly reports the taint leak.In my sources_sinks.pysa I declare
source
andsink
as taint sources and sinks respectively (this config works as we can see with the detected leak inmy_function
):I call pysa via
pyre analyze --save-results-to ./results/ --infer-self-tito
and I'm using version 0.9.23The text was updated successfully, but these errors were encountered: