Revision as of 16:46, 6 February 2019

OWASP Project Requests

Tips to get you started in no particular order:

* Read Google Summer of Code Program(GSOC)`
* Read the GSoC SAT 
* Read the GSOC Student Guidelines
* Contact us through the mailing list or irc channel.
* Check our github organization

OWASP-SKF (draft)

Idea 1:

Build lab examples and write-ups (how to test) for different vulnerabilities over different technology stacks. These challenges are to be delivered in Docker so they can be

easily deployed.

In the current situation the security knowledge framework ultimately presents a list of security controls with correlating knowledge base items that contain a description and

a solution. The new labs are used to give the software developers or application security specialists a more in depth understanding and approach on how to test the

vulnerabilities in their own code.

• For example we have now around 20 lab challenges in Docker container build in Python:
  • A Local File Inclusion Docker app example:
    • https://github.com/blabla1337/skf-labs/tree/master/LFI
  • A write-up example:
    • https://owasp-skf.gitbook.io/asvs-write-ups/filename-injection

The images that are pushed to the Github repository are already automatically build and pushed to a docker registry where the SKF users can easily pull the images from to get their

labs running. Of course they can download it and build it themselves from source by pulling the original repository.

Idea 2:

We want to extend the Machine learning chatbot functionality in SKF.

• Create a desktop version of the chatbot. Where people can install the setup file on their local machine.
• Extend the bots capability to do the google search(using web scraping) for the things which are not available in the database. So, it will have a wider scope of knowledge.
• Extend the bot capability to reply what security controls should be followed from the ASVS and MASVS or other custom checklists that are present in SKF.
• Extend the bot to different platforms like Facebook, telegram, slack etc.
  • Now the working chatbot implementation for example is only for Gitter

OWASP DefectDojo

OWASP DefectDojo is a popular open source vulnerability management tool, used as the backbone for security programs. It is easy to get started with and work on! We welcome volunteers of all experience levels and are happy to provide mentorship.

Option 1: Unit Tests - Difficulty: Easy

• If you're new to programming, unit tests are short scripts designed to test a specific function of an application.
• The project needs additional unit tests to ensure that new code functions properly.

Option 2: Feature Enhancement - Difficulty: Varies

• The functionality of DefectDojo is constantly expanding.
• Feature enhancements offer programming challenges for all levels of experience.

Option 3: Pull Request Review - Difficulty: Moderate - Hard

• Test pull requests and provide feedback on code.

OHP (OWASP Honeypot)

OWASP Honeypot is an open source software in Python language which designed for creating honeypot and honeynet in an easy and secure way! This project is compatible with Python 2.x and 3.x and tested on Windows, Mac OS X and Linux.

Getting Start

It's best to start from GitHub wiki page, we are looking forward to add more modules and optimize the core.

Technologies

Currently we are using

• Docker
• Python
• MongoDB
• TShark
• Flask
• ChartJS
• And more linux services

Expected Results

...

Roadmap

...

Students Requirements

• Python
• Packet Analysis
• Docker
• Database

Mentors and Leaders

• Ali Razmjoo (Mentor & Project Leader)
• Ehsan Nezami (Mentor & Project Leader)
• Reza Espargham(Mentor)
• Abbas Naderi (Mentor)

OWASP Juice Shop

OWASP Juice Shop Project is an intentionally insecure webapp for security trainings written entirely in Javascript which encompasses the entire OWASP Top Ten and other severe security flaws. Juice Shop is written in Node.js, Express and Angular. The application contains more than 30 challenges of varying difficulty where the user is supposed to exploit the underlying vulnerabilities. Apart from the hacker and awareness training use case, pentesting proxies or security scanners can use Juice Shop as a "guinea pig"-application to check how well their tools cope with Javascript-heavy application frontends and REST APIs.

The best way to get in touch with us is the community chat on https://gitter.im/bkimminich/juice-shop. You can also send PMs to the potential mentors (@bkimminich, @wurstbrot and @J12934) there if you like!

To receive early feedback please put your proposal on Google Docs and submit it to the OWASP Organization on Google's GSoC page in Draft Shared mode. Please pick juice shop as Proposal Tag to make them easier to find for us. Thank you!

Challenge Pack 2019

Brief Explanation:

Ideas for potential new hacking challenges are collected in GitHub issues labeled "challenge". This project could implement a whole bunch of challenges one by one and release them over the course of several small releases. This would allow the student to work in a professional Continuous Delivery kind of way while bringing benefit to the Juice Shop over the duration of the project.

Coming up with good additional ideas for challenges in the proposal could make the difference between being selected or declined as a student for this project!

Expected Results:

• 10 or more new challenges for OWASP Juice Shop (including required functional enhancements to place the challenges)
• Each challenge comes with full functional unit and integration tests
• Each challenge is verified to be exploitable by corresponding end-to-end tests
• Hint and solution sections for each new challenge are added to the "Pwning OWASP Juice Shop" ebook
• Code follows existing styleguides and passes all existing quality gates regarding code smells, test coverage etc.

Getting started:

• Get familiar with the architecture and code base of the application's rich Javascript frontend and RESTful backend
• Get a feeling for the high code & test quality bar by inspecting the existing test suites and static code analysis results
• Get familiar with the CI/CD process based on Travis-CI and several associated 3rd party services

Knowledge Prerequisites:

• Javascript, Unit/Integration testing, experience with (or willingness to learn) Angular and NodeJS/Express, some security knowledge would be preferable.

Mentors:

• Bjoern Kimminich - OWASP Juice Shop Project Leader
• Timo Pagel - OWASP Juice Shop Project Collaborator
• Jannik Hollenbach - OWASP Juice Shop Project Collaborator

Hacking Instructor

Brief Explanation:

While the Juice Shop is offering a lot of long-lasting motivation and challenges for security experts, it might be a bit daunting for newcomers and less experienced hackers. The "Hacking Instructor" as sketched in GitHub issue #440 could guide users from this target audience through at least some of the hacking challenges. As this would be an entirely new and relatively independent feature of the Juice Shop, students should be able to bring in their own creativity and ideas a lot.

For this project, a good proposal with a design & implementation proposal more sophisticated than the rough ideas in #440 is paramount to be selected as a student!

Expected Results:

• A working implementation of e.g. an avatar-style "Hacking Instructor" or other solution based on the students own proposal
• Coverage of at least the trivial (1-star) and some easy (2-star) challenges
• Documentation how to configure or script the "Hacking Instructor" for challenges in general

Getting started:

• Get familiar with the architecture and code base of the application's rich Javascript frontend and RESTful backend
• Get a feeling for the high code & test quality bar by inspecting the existing test suites and static code analysis results
• Get familiar with the CI/CD process based on Travis-CI and several associated 3rd party services

Knowledge Prerequisites:

• Javascript, Unit/Integration testing, experience with (or willingness to learn) Angular, some UI/UX experience would be preferable.

Mentors:

• Bjoern Kimminich - OWASP Juice Shop Project Leader

Your idea

Brief Explanation:

You have an awesome idea to improve OWASP Juice Shop that is not on this list? Great, please submit it!

Getting started

• Get in touch with Bjoern Kimminich

Expected Results:

• A new feature that makes OWASP Juice Shop even better
• Code follows existing styleguides and passes all existing quality gates regarding code smells, test coverage etc.

Knowledge Prerequisites:

• Javascript, Unit/Integration testing, experience with (or willingness to learn) Angular and NodeJS/Express, some security knowledge would be preferable.

Mentors:

• Bjoern Kimminich - OWASP Juice Shop Project Leader

OWASP-Securetea Tools Project

The purpose of this application is to warn the user (via various communication mechanisms) whenever their laptop accessed. This small application was developed and tested in python in Linux machine is likely to work well on the Raspberry Pi as well. - https://github.com/OWASP/SecureTea-Project/blob/master/README.md

Brief Explanation

We are looking any awesome idea to improve Securetea Project that is not on this list? We are expecting make this project will be useful to everyone to secure their Small IoT.

Idea

Below roadmap and expect results you can choose to improve Securetea Project . if any bugs please help to fix it

Roadmap

See Our Roadmap
https://github.com/OWASP/SecureTea-Project#roadmap
Notify by Twitter (done)
Securetea Dashboard / Gui (done)

Expect Results

Securetea Protection /firewall
Securetea Antivirus
Notify by Whatsapp
Notify by SMS Alerts
Notify by Line
Notify by Telegram
Intelligent Log Monitoring
Login History

Students Requirements

• Python
• Javascript
• Angular and NodeJS/Express
• Database
• Linux

Mentors

• Ade Yoseman Putra - (OWASP Securetea Project Leader)
  
• Rejah Rehim.A.A]- (OWASP Securetea Project Leader)
• Ananthu S - (Mentor)

OWASP OWTF

Offensive Web Testing Framework (OWTF) is a project focused on penetration testing efficiency and alignment of security tests to security standards like the OWASP Testing Guide (v3 and v4), the OWASP Top 10, PTES and NIST. Most of the ideas below focus on rewrite of some major components of OWTF to make it more modular. OWTF is moving to a fresh codebase with a fully Docker testing and deployment environment. If you want to get a jumpstart, check out https://github.com/owtf/owtf/tree/new-arch.

OWASP OWTF - MiTM proxy interception and replay capabilities

Brief Explanation:

The OWTF man-in-the-middle proxy is written completely in Python (based on the excellent Tornado framework) and was benchmarked to be the fastest MiTM python proxy. However it lacks the useful and much need interception and replay capabilities of mitmproxy (https://github.com/mitmproxy/mitmproxy).

The current implementation of the MiTM proxy serves its purpose very well. Its fast but its not extensible. There are a number of good use cases for being extensible

• ability to intercept the transactions
• modify or replay transaction on the fly
• add additional capabilities to the proxy (such as session marking/changing) without polluting the main proxy code

Bonus:

• Design and implement a proxy plugin (middleware) architecture so that the plugins can be defined separately and the user can choose what plugins to include dynamically (from the web interface).
• Replace the current Requester (based on urllib, urllib2) with a more robust Requester based on the new urllib3 with support for a real headless browser factory. The typical flow when requested for an authenticated browser instance (using PhantomJS)

• The "Requester" module checks if there is any login parameters provided (i.e form-based or script - look at https://github.com/owtf/login-sessions-plugin)
• Create a browser instance and do the necessary login procedure
• Handle the browser for the URI
• When called to close the browser, do a clean logout and kill the browser instance.

Expected results:

• IMPORTANT: PEP-8 compliant code in all modified code and surrounding areas.
• IMPORTANT: OWTF contributor README compliant code
• IMPORTANT: Sphinx-friendly python comments example Sphinx-friendly python comments here
• CRITICAL: Excellent reliability
• Good performance
• Unit tests / Functional tests
• Good documentation

Knowledge Prerequisite: Python proficiency, some previous exposure to security concepts and penetration testing is welcome but not strictly necessary as long as there is will to learn.

OWASP OWTF Mentors: Contact: Abraham ArangurenViyat BhalodiaBharadwaj Machiraju OWASP OWTF Project Leaders

OWASP OWTF - Web interface enhancements

Brief explanation:

The current web interface is a mixture of Tornado Jinja templates and ReactJS. A complete UI change to a stable ReactJS-based interface should be the deliverable for this project. Most of the hard part for the change has already been done and added in a separate branch at https://github.com/owtf/owtf/tree/develop.

For background on OWASP OWTF please see: https://www.owasp.org/index.php/OWASP_OWTF

Expected results:

• IMPORTANT:Clean, maintainable (ES6 compatible and using recommended design patterns) React (JavaScript) code. (This is a good example!)
• IMPORTANT: Thoroughly documented code along with API examples and example future components.
• CRITICAL: Excellent reliability and performance.
• Unit tests / Functional tests and easy to setup testing environment (preferably automated).

Knowledge Prerequisite: Python (reading API source code and endpoints), React.JS (high proficiency) and general JavaScript proficiency.

OWASP OWTF Mentors: Contact: Abraham ArangurenViyat BhalodiaBharadwaj Machiraju OWASP OWTF Project Leaders

OWASP OWTF - New plugin architecture

Brief explanation:

The current plugin system is not very useful and it is painful to browse many plugins. Most of the plugins do have much code and most of is repeated - much refactoring needed there.

This issue is documented in detail at https://github.com/owtf/owtf/issues/905.

For background on OWASP OWTF please see: https://www.owasp.org/index.php/OWASP_OWTF

Expected results:

• IMPORTANT: PEP-8 compliant code in all modified code and surrounding areas.
• IMPORTANT: OWTF contributor README compliant code
• IMPORTANT: Sphinx-friendly python comments example Sphinx-friendly python comments here
• CRITICAL: Excellent reliability
• Good performance
• Unit tests / Functional tests
• Good documentation

OWASP iGoat (draft)

Idea 1: Completing OWASP iGoat documentation at https://docs.igoatapp.com/ and creating demo videos at for OWASP iGoat YouTube channel for learning purpose.

Idea 2: Adding new challenge pack / CTF for iGoat. It should be one point solution for learning iOS app security

OWASP Seraphimdroid

Idea 1: Anomaly detection of device state

The idea is that certain features of a device would be constantly monitored (battery use, internet usage, opp calls, etc.). Initially, the usual behaviour of the device would be learned. Later, anomalies normal behavior would be reported to the user. This should involve some explanations, such as which applications are causing an anomaly the device behaviors

Idea 2: On device machine learning of maliciousness of an app

Tensor-flow for on-device processing and some other libraries have been released that enable machine learning. We have previously applied a system, that based on permissions, is able to distinguish malicious apps from non-malicious. Now, we would like to learn also from other outputs and things one can monitor about application whether it can be malicious.

Idea 3: Enhansing privacy features

The vision of Seraphimdroid is to be aware of privacy threats. This may be achieved throug knowing which applications are using user accounts or other information that user has on phone to send to the server, or just by knowing which applications may be doing it. Knowledge base should be extending with the suggestions on how to improve privacy. Also, automated settings of various apps to use encryption should be proposed.

OWASP ZAP

OWASP Zed Attack Proxy Project (ZAP) The OWASP Zed Attack Proxy (ZAP) is one of the world’s most popular free security tools and is actively maintained by hundreds of international volunteers. Previous GSoC students have implemented key parts of the ZAP core functionality and have been offered (and accepted) jobs based on their work on ZAP.

Active Scanning WebSockets

Brief Explanation:

ZAP has good support for websockets, and allows them to be intercepted, changed and fuzzed. Unfortunately it doesn't currently support active scanning (automated attacking) of websocket traffic (messages).

We would like to add active scanning support to websockets, ideally in a generic way which would allow us to reuse as many of our existing rules as are relevant. Adding additional websocket specific attacks would also be very useful.

This project will be a continuation of the work that was started as part of last year's GSoC.

Expected Results:

• An pluggable infrastructure that allows us to active scan websockets
• Converting the relevant existing scan rules to work with websockets
• Implementing new websocket specific scan rules

Getting Started:

• Have a look at the ZAP CONTRIBUTING.md file, especially the 'Coding' section.
• We like to see students who have already contributed to ZAP, so try fixing one of the bugs flagged as IdealFirstBug.

Knowledge Prerequisites:

• ZAP is written in Java, so a good knowledge of this language is recommended. Some knowledge of application security would be useful, but not essential.

Mentors: Simon Bennetts @ and the rest of the ZAP Core Team

Automated Authentication Detection and Configuration

Brief Explanation:

Currently a user must manually configure ZAP to handle authentication, eg as per https://github.com/zaproxy/zaproxy/wiki/FAQformauth

This is time consuming and error prone.

Ideally ZAP would help detect login and registration pages and provide more assistance when configuring authentication, ideally being able to completely automate the task for as many sort of webapps as possible.

This project will be a continuation of the work that was started as part of last year's GSoC.

Expected Results:

• Detect login and registration pages
• Provide a wizard to walk users through the process of setting up authentication, with as much assistance as possible
• An option to completely automate the authentication process, for as many authentication mechanisms as possible

Getting Started:

• Have a look at the ZAP CONTRIBUTING.md file, especially the 'Coding' section.
• We like to see students who have already contributed to ZAP, so try fixing one of the bugs flagged as IdealFirstBug.

Knowledge Prerequisites:

• ZAP is written in Java, so a good knowledge of this language is recommended. Some knowledge of application security would be useful, but not essential.

Mentors: Simon Bennetts @ and the rest of the ZAP Core Team