Help write a CodeQL query for the Gradio framework #870
Replies: 2 comments 1 reply
-
|
Hi @NgocKhanhC311 👋🏻 You say that you're getting results when you evaluate If I look at the code you linked to, it seems that the call to |
Beta Was this translation helpful? Give feedback.
-
|
Hey @mbg! The question was also asked on our public Slack and we got the solution there—sources and sinks were found correctly, but it turned out we needed an additional taint step 👍 Pasting my answer from Slack, so others can have use of it: In short, it’s a corner case. You can make the flow work and report an alert if you add a Taint Step to Taint Tracking: The above specifically works for cases when To explain: there are cases, which might make the data flow not propagate. In this case, CodeQL flowed to When running this query, I get the result you are looking for. You can also try it with the wildcard by replacing |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi team,
I'm new to CodeQL. I read this article and want to write a practice query. I tried looking for the sink (os.path.basename) and using the methods passed in from gradio’s interface as the source. If I run each query separately in isSource and isSink, I do get results, but I want to observe the flow of the source code. Unfortunately, it’s not working.
Please help me.
Beta Was this translation helpful? Give feedback.
All reactions