-
I get this strange behavior in VSCode CodeQL extension. I think I am missing something but I don't know what. The excerpt of the query is: /**
* @name name
* @description descr
* @kind path-problem
* @id py/uid
* @security-severity 7.5
* @precision high
* @tags security
* experimental
* external/cwe/cwe-123
*/
import python
//import semmle.python.dataflow.new.DataFlow
import semmle.python.dataflow.new.TaintTracking
import semmle.python.dataflow.new.RemoteFlowSources
import semmle.python.Concepts
import semmle.python.ApiGraphs
import DataFlow::PathGraph
import semmle.python.dataflow.new.internal.DataFlowPublic
class Config extends TaintTracking::Configuration {
Config() { this = "uid" }
// override isAdditionalTaintStep + isSanitizer + isSink + isSource (RemoteFlowSource).
}
from Config config, DataFlow::PathNode source, DataFlow::PathNode sink
where config.hasFlowPath(source, sink)
select sink, source, sink, "A potential sweet catch " I get these results in alerts mode, it is supposed to give me results in PATH view format, right? PS: One last detail ... please, I sometime comment the query part while leaving the class as-is, and modify the Thank you in advance. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
It is normal for the view to be named "alerts" even if there are associated paths. It is also normal for the path dropdown not to appear if the path is of length 1 (i.e., usually if the source and sink are in the same function). Could you give example Python and QL that produces an unexpected result? |
Beta Was this translation helpful? Give feedback.
It is normal for the view to be named "alerts" even if there are associated paths. It is also normal for the path dropdown not to appear if the path is of length 1 (i.e., usually if the source and sink are in the same function). Could you give example Python and QL that produces an unexpected result?