New output format - Githubissues

Sinderella / epherousa

1 stars 0 forks source link

New output format #15

Open Sinderella opened 7 years ago

Sinderella commented 7 years ago

Tables' format's gone wrong quite frequent

Sinderella commented 7 years ago

Nick's idea

./ephe drupal sql inje

./ephe -c CVE-xxxx-xxxx

INFO from exploit db
----
INFO Exploit info
  DATE CVE-1324-5315
  DESC
  URL
INFO CVEDETAILS shown 
  Desc CVEDETAILS - highlioghting etc
  - CVSS 6
  - Range Remote
  - Unauth/Auth
  - xxx

  References (uniq)
  * 
  *
  *
  *

----

INFO Seucirytfocus
  DATE N/A
  DESC
  URL
INFO CVEDETAILS shown
  ******

----

INFO Core Impact

INFO CVE STUFF WITHOUT EXPLOITS

INFO Exploit info
  *****
INFO CVEDETAILS shown
    Desc CVEDETAILS - highlioghting etc
  - CVSS 8
  - Range Remote
  - xxx
  - xxx

  References
  * 
  *
  *
  *

DATE CVE-1324-5315
DESC
URL
URL2
URL3

ngkogkos commented 7 years ago

First I need to do a mockup
Implement it initially and see how it looks like
If we like it we can play more with options, add the reporting system and database to store the CVE Info with which a user can then call ephe with special args and lookup the CVE locally

ngkogkos commented 7 years ago

I was thinking of it further, I don't like the above output as it has multiple-info occurrence issues. What if:

We go with mockup A, where CVE details are printed in the bottom
Implement SQLite3 info storing
Allow users to either scroll through all that long output or provide a CVE for which we will return all the relevant info from the SQLite3 db.
For returning the info, as you said, they will have to rerun ephe with a special switch + CVE or maybe the previous searches ID ?