search

j3ssie / osmedeus

A Workflow Engine for Offensive Security
https://osmedeus.org/
MIT License
5.33k stars 879 forks source link

Feature Request & Suggestions #52

Closed ResistanceIsUseless closed 2 years ago

ResistanceIsUseless commented 5 years ago

Been trying it out and so far I like the idea. I do feel like it's a bit of information overload and doesnt really help with parsing the information in a way to help you look for bugs. It might because mine freezes or takes too long and never finishes. i really like the way that whatweb parses out the relevant information so it would be nice if you could find a way to do that as well as have it grab content using meg and parse out headers and any parameters found. I'm picturing two types of flows here. 1. Your currently flow that pretty much grabs everything with a more complete hierarchy of multiple steps based on findings. 2. A second more customized flow that allows you to create a custom hierarchy with either your own logic. Here is an example:

subfinder
 |----subjack
 |----assetfinder 
               |-----httprobe|whatweb (IP & DNS)
                             |-----fuff|gobuster
                             |         \----nikto (IP & DNS)
                             |                     \---- Logic (if URL contains X)
                             |                                 \----droopscan(IP & DNS)
                             |                                   \----wpscan(IP & DNS)
                             |-----meg
                                        |----nikto (IP & DNS)
                                        |----snallygaster (IP & DNS)
                                        |---- Logic (if URL contains X)
                                        |           \----droopscan(IP & DNS)
                                        |             \----wpscan(IP & DNS)
                                        |----proxy
                                        |           \----burp (IP & DNS)
                                        |----gf

Hopefully that makes sense, since you already have some logic in place but it would be nice to be able to customize by adding logic for more details actions as well as adding additional tools. other options might include.

Also it might be nice to have the following tools as part of the modules: snallygaster nikto whatweb droopscan parsero fuff (to replace wfuzz)

I'm sorry for the long message and all the crazy ideas. If you would actually be interested in anything I mentioned and don't mind my intermediate python skills I'm always willing to chip in. I've been working on my own version of reconscan(its a popular automation script for OSCP) which might also be helpful for enumeration of scanning services.

j3ssie commented 5 years ago

Thanks for your suggestion.

The main purpose of Osmedeus is discovering as much as target as possible and also find the potential target also. Anyway, I’m planning to add a way to easily to view result and logging every section.

Your idea is focussing on a single target which is I'm also planning to do more about it but currently, Osmedeus doesn't have a real DB so I considering to build a real DB for it or do it as a plugins for my new tool.

Just DM me via @j3ssie for any question.

j3ssie commented 2 years ago

The issue is no longer exist due to the repo having been upgraded to Osmedeus Next Generation v4.0