|
Now the following code, known index function first parameter request is user input can be used as a source, and then now known to deserialize function points in Tools#deserialize function, can be used as a sink. how to write QL rules to query this vulnerability? Code: I've written a rule, but it's a bit flawed and doesn't fully check out the entire path of request->bytes. my ql rules: |
Answered by
smowton
Apr 7, 2021
Replies: 1 comment 9 replies
|
This looks like it's working fine -- the source at |
9 replies
Answer selected by
SummerSec
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

This looks like it's working fine -- the source at
getValueis detected,base64Decodeis known to propagate taint, thenTools.deserializeis recognised as the sink. What's the problem?