Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Improve Exploiters documentation #709

Closed
11 tasks
ShayNehmad opened this issue Jul 5, 2020 · 4 comments
Closed
11 tasks

Improve Exploiters documentation #709

ShayNehmad opened this issue Jul 5, 2020 · 4 comments
Labels
Complexity: Low Documentation Issues relating to the project's documentation like readme files, guides, etc. Impact: Low

Comments

@ShayNehmad
Copy link
Contributor

ShayNehmad commented Jul 5, 2020 •
edited
Loading

Documentation request

Add a new page 🆕

What documentation you'd like us to add?

Add a reference for each of the following attacks:

  • Bruteforce (one for each protocol?)
  • Shellshock
  • ElasticGroovy
  • Hadoop
  • MSSQL
  • SambaCry
  • Struts2
  • VSFTPD
  • Weblogic
  • MS08-067
  • WMI

What (at least) should each one include?

  • A link to CVE DB/MITRE/external resource
  • A short explanation of how the exploit works
  • A link to "how to enable/disable exploiters" in the config documentation

Where in the documentation tree?

Create a new section called "Reference" and create a chapter under that called "Exploits"
@ShayNehmad ShayNehmad added the Documentation Issues relating to the project's documentation like readme files, guides, etc. label Jul 5, 2020
@acepace
Copy link
Contributor

acepace commented Jul 15, 2020

can I propose a sample one?

@ShayNehmad
Copy link
Contributor Author

https://staging-covuyicu.kinsta.cloud/infectionmonkey/docs/reference/exploiters/

@itaymmguardicore itaymmguardicore modified the milestone: 1.9.0 Aug 11, 2020
@itaymmguardicore itaymmguardicore changed the title Exploiters documentation Improve Exploiters documentation Aug 11, 2020
@VakarisZ
Copy link
Contributor

IMO we should prioritize migrating the rest of our dev docs. Enough info should be provided on the exploiter selector itself, for a person to google stuff if he wishes to.

@ilija-lazoroski
Copy link
Contributor

Suppressed by #4213

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Complexity: Low Documentation Issues relating to the project's documentation like readme files, guides, etc. Impact: Low
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@acepace @ilija-lazoroski @itaymmguardicore @VakarisZ @ShayNehmad