JS Analyzing #1173
Replies: 6 comments 3 replies
-
These are both good ideas. It would be cool to have a family of modules for downloading and analyzing javascript. The use case is different enough I think it would justify having a separate module to download them. @liquidsec what are your thoughts |
Beta Was this translation helpful? Give feedback.
-
Maybe also add headless ability of downloading dynamically loaded js in DOM |
Beta Was this translation helpful? Give feedback.
-
One method explained here by one of the guys I follow in Oasis discord channel, originally can be seen here: |
Beta Was this translation helpful? Give feedback.
-
Maybe not a bad idea for https://www.redsentry.com/blog/javascript-source-maps This may be helpful too https://www.jswzl.io/ and see what can achieve in bbot. Sample of the source map |
Beta Was this translation helpful? Give feedback.
-
May be useful, made by the person above for JS analyzing: |
Beta Was this translation helpful? Give feedback.
-
Probably the thing I'm going to write here, is not related to bbot at all and be out of scope of it, but I'm writing it anyway, maybe someone came up with better idea or a module.
Right now I am downloading JS files by filedownload module. Then I'm going to use this script to find dangerous sinks and sources inside them:
https://github.com/ariary/DomXssFinder
(You can see info about these sources and sinks here: https://github.com/Sivnerof/Sources-And-Sinks-Cheatsheet )
I was thinking maybe can automate this and add this to bbot that shows which sources and sinks exist in which files.
Also, bbot is not downloading inline js. Not sure if that is even technically possible to implement in bbot, but right now I'm using this to download them if needed:
https://github.com/ariary/JSextractor/
Beta Was this translation helpful? Give feedback.
All reactions