A pytest-inspired, DAST framework, capable of identifying vulnerabilities in a distributed, micro-service ecosystem through chaos engineering testing and stateful, Swagger fuzzing.
Other
205
stars
25
forks
source link
Non-valuable data is propagated through request sequences #65
Hi Team!
While testing Fuzz-lightyear against Mozilla Kinto we have faced with issue related with propagating non-valuable data through request sequences.
Could you please check our results?
While generating a sequence of requests method add_response() called with some response as an input:
To extract data add_response() use for loop with dir(response).
But in that case dir(response) equals to
Hi Team! While testing Fuzz-lightyear against Mozilla Kinto we have faced with issue related with propagating non-valuable data through request sequences. Could you please check our results?
While generating a sequence of requests method add_response() called with some response as an input:![image](https://user-images.githubusercontent.com/22557771/101356878-c2936480-38a9-11eb-9f3a-1c01bce97ec4.png)
To extract data add_response() use for loop with dir(response). But in that case dir(response) equals to
As a result we have non-valuable data in self.data (this data is used to construct nest request in a sequence):![image](https://user-images.githubusercontent.com/22557771/101357433-78f74980-38aa-11eb-9310-3a1be192ed4b.png)
Seems that we should use response.keys() instead of dir(response):
Do we miss something in our reasoning? Are there any cases when dir(response) is needed?