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
It seems that the two concepts of "vulnerability" and "anomaly" could benefit from being abstracted with a class. We could for example add a Vulnerability class, and a XSSVulnerability as a inherited class (an one for each vulnerability).
This could also help with the reporting, because each class could be responsible for formatting its instances into each format (txt, html, etc).
Would you be interested in seeing more contributions going this way?
The text was updated successfully, but these errors were encountered:
Indeed I already thought of that formatting problem but not about classes inheritance fir vulnerabilities. It seems to be a good idea and of course I'm not against such contributions :)
In the attack module, some parameters are often used together in functions. For example:
wapiti/wapitiCore/attack/mod_xss.py
Lines 172 to 179 in 4366708
It seems that the two concepts of "vulnerability" and "anomaly" could benefit from being abstracted with a class. We could for example add a
Vulnerability
class, and aXSSVulnerability
as a inherited class (an one for each vulnerability).This could also help with the reporting, because each class could be responsible for formatting its instances into each format (txt, html, etc).
Would you be interested in seeing more contributions going this way?
The text was updated successfully, but these errors were encountered: