This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of "OWASP Pyttacker Project"

From OWASP
Jump to: navigation, search
 
(One intermediate revision by the same user not shown)
Line 12: Line 12:
 
==Introduction==
 
==Introduction==
  
Most of the time is spent on finding the bad stuff during a Web PenTest, reports are time consuming and you need to deliver your results as soon as possible, however in the end the one that will need to fix the issue (or push others to do it) will need to really understand the impact of the findings included in a report. When you show raw Database data from a SQLi it's very visible for your costumer that the impact is High, however when the finding need some other factors the impact become more complicated to be demonstrated to non technical people, just a request and response is not enough and how long are you willing to take in order to create a nice screenshot for being included in your report.
+
Most of the time is spent on finding the bad stuff during a Web PenTest, writing reports is time consuming and you need to deliver the results as soon as possible, however in the end the one that will need to fix the issue (or push others to do it) will need to really understand the impact of the findings included in the report. When you show raw Database data from a SQLi it's very visible for your costumer that the impact is High, however when the finding need some other steps for being reproduced the impact become more complicated to be demonstrated to non technical people, just a "request" and "response" is not enough and how long are you willing to take for coding a working PoC and create a nice screenshot for being included in your report.
  
What about using "something" that is the server you mention as 'evil.com' that can be used by the bad guys against your costumer's company, even better if you know that the evil server is not that "evil" and you can validate, modify or disable it's contents, would be nice to have "something" for creating nice screen-shots, what about reproducing the finding during that meeting when your are trying to show the impact of your findings, not just a pop-up alert for XSS, what if you show an inoffensive but scaring partial defacement or a javascript keylogger in action.
+
What about using "something" that is the server you mention as hypothetic 'evil.com' that can be used by the bad guys against your costumer's company, even better if you know that the evil server is not that "evil" and you have full control of it, would be nice to have "something" handy and portable for reproducing those findings and grab nice screen-shots, what about reproducing the finding during that meeting when you are trying to show the impact of your findings, not just a pop-up alert for XSS, what if you show an inoffensive but scaring partial defacement or a javascript keylogger in action.
  
If you agree then Pyttacker will be an interesting tool for you
+
Sounds good ? if yes then Pyttacker will be an interesting tool for you
  
  
Line 62: Line 62:
 
* [25 March 2014] Project created
 
* [25 March 2014] Project created
 
* [26 April 2014] New Alpha made public
 
* [26 April 2014] New Alpha made public
 +
* [29 July 2015] Improvements were added
  
 
==Classifications==
 
==Classifications==

Latest revision as of 15:59, 18 December 2015

OWASP Project Header.jpg

OWASP Pyttacker Project

The OWASP Pyttacker Project is a portable Web Server that include the features needed for every Pentester when creating reports, helping to create PoCs that show a more descriptive way to create awareness to the businesses by demonstrating realistic but inoffensive "attacks" included as part of the tool.

Introduction

Most of the time is spent on finding the bad stuff during a Web PenTest, writing reports is time consuming and you need to deliver the results as soon as possible, however in the end the one that will need to fix the issue (or push others to do it) will need to really understand the impact of the findings included in the report. When you show raw Database data from a SQLi it's very visible for your costumer that the impact is High, however when the finding need some other steps for being reproduced the impact become more complicated to be demonstrated to non technical people, just a "request" and "response" is not enough and how long are you willing to take for coding a working PoC and create a nice screenshot for being included in your report.

What about using "something" that is the server you mention as hypothetic 'evil.com' that can be used by the bad guys against your costumer's company, even better if you know that the evil server is not that "evil" and you have full control of it, would be nice to have "something" handy and portable for reproducing those findings and grab nice screen-shots, what about reproducing the finding during that meeting when you are trying to show the impact of your findings, not just a pop-up alert for XSS, what if you show an inoffensive but scaring partial defacement or a javascript keylogger in action.

Sounds good ? if yes then Pyttacker will be an interesting tool for you


Licensing

OWASP Pyttacker is free to use. It is licensed under GNU GPL v3 License (allows commercial use, but requires that modifications to your code stay open source, thus prohibiting proprietary forks of your project)


What is the OWASP Pyttacker Project?

Key characteristics:

  • Minimal requirements (Just Python and a Web Browser)
  • Cross-platform
  • Portable
  • Easy Plug-ins Implementation
  • Easy to use


Project Leader

Mario Robles


Supporters


Quick Download

git clone https://github.com/RoblesT/pyttacker.git

Manual and How-to

Timeline

  • [25 March 2014] Project created
  • [26 April 2014] New Alpha made public
  • [29 July 2015] Improvements were added

Classifications

Owasp-incubator-trans-85.png Owasp-builders-small.png
Owasp-defenders-small.png
Cc-button-y-sa-small.png
Project Type Files TOOL.jpg

Have questions ?

Send a message or Subscribe

How to get?
Download it Here or follow the instructions Here
How to install?
It is portable, no installation is required for using it
Where can I use it?
The tool is coded in Python and has been tested on Linux (Ubuntu, Kali, Samurai), MAC and Windows


Volunteers

Pyttacker is developed by a worldwide team of volunteers. The primary contributors to date have been:

  • Mario Robles

Join us ! or Subscribe

As of March 2014, the priorities are:

"First Alpha version is ready but need more development time for including features that can be delegated to newcomers since the project is module based. The First Beta release is intended to be published on June 2014 including the PoC modules for CSRF, XSS, Open Redirect, XFS Next Steps:

  1. Add more PoC modules for more Vulnerabilities
  2. Add integration with tools like OWASP ZAP and Burp Suite"

Involvement in the development and promotion of Pyttacker is actively encouraged! You do not have to be a security expert in order to contribute. Some of the ways you can help:

  • QA Testing | Bug reporting
  • Content Translation
  • Plugin Development
  • Core code improvements


PROJECT INFO
What does this OWASP project offer you?
RELEASE(S) INFO
What releases are available for this project?
what is this project?
Name: OWASP Pyttacker Project (home page)
Purpose: Pyttacker is a portable Web Server that include the features needed for every Pentester when creating reports, helping to create PoCs that show a more descriptive way to create awareness to the businesses by demonstrating realistic but inoffensive "attacks" included as part of the tool.
License: GNU GPL v3 License (allows commercial use, but requires that modifications to your code stay open source, thus prohibiting proprietary forks of your project)
who is working on this project?
Project Leader(s):
  • Mario Robles @
how can you learn more?
Project Pamphlet: Not Yet Created
Project Presentation:
Mailing list: Mailing List Archives
Project Roadmap: View
Key Contacts
  • Contact Mario Robles @ to contribute to this project
  • Contact Mario Robles @ to review or sponsor this project
current release
Not Yet Published
last reviewed release
Not Yet Reviewed


other releases