Difference between revisions of "OWASP Autumn of Code 2006 - Applications"

Jump to: navigation, search
(AoC 18 -)
(AoC 19 -)
Line 621: Line 621:
== AoC 19 - ==
== AoC 19 - thomas ==
ups - and now its to late, for they closed the owasp automn of code early 9/18th.
i just wanted to ask about participating on owasp's automn of code with checkomatik - a project for managing checks and reports.
checkomatik is based on php/mysql, brings a defined check-template with a handful of predefined texts and checks to a simple webinterface.
simple checks like nikto, bannergrabs, whois and so on get handled either by serversniff.net/ (see http://www.serversniff.net/wiki_en/index.php?title=API) or by own functions and scripts.
the goal of the project is to handle and automate the doing, archiving and report of  my (somewhat standartized) pen-tests whilst be as flexible as possible e.g. to add additional servers, ips, texts etc. to any check i do.
checks are extensible and completely self-defineable.
There is currently an export to pseudo-xml, we are working on odf, rtf and simple html.
I'm using a custom version of checkomatik this since 2 years for my pentests - but i'd need some ressources to refine this for publishing. the code is messy, its not completely multiuser-capable, and its ugly. there is a playground of the actual stage of development at http://serversniff.net/checkomatik
nevermind if its to late anyway,
== AoC 20 - ==
== AoC 20 - ==

Revision as of 18:01, 21 September 2006

AoC 1 - Paolo :

Hi Dinis, the Owasp autumn of Code idea is great and it would be greate for me to partecipate. This is my submission informations:

1) Contact details ...........

2) Which project you want to be involved in I'd like to be involved in Code Review project

3) Why you should be sponsored for the project I've got a very strong background in software development. I reached a good C programming level (working at kernel level in Linux operating system) and a good Java programming level in web application development field. My working field is however security as pen tester and code reviewer and I want to merge these two main field of interest: security and code.

I think I can improve Code Review project merging my theorical experience (writing doc about code review, secure coding and providing code snippets in various languages as a sort of Sample Library or knowledge base) with my pratical attidute. Looking ad Owasp LAPSE project, it would be a great idea to create a sort of common API building a sort of "code review tool engine".

This engine would be generic and devoted ONLY to code review related aspects. Using such engine as basis we could build a pletora of tools providing code review capability for common os IDE (extending LAPSE for eclipse, netbeans, ...) and for ad hoc command line tool.

4) What are the objectives and deliverables My objectives are:

  • focusing people attention about how much code review and safe coding important are
  • providing people practical instruments to test their applications or to build their testing tool too

My deliverables are:

  • improving Code Review project documentation for my first objective
  • realize the engine core complete with a set of well known wrong code practice, providing a way to extend such engine and to provide a PoF testing tool using the aformentioned APIs

AoC 2 - Federico


I would like to apply for OWASP’s AOC as an individual, with no relation to or sponsorship from PaySett.com (my current employer)

I would like to work on either the HoneyComb project (Especially the Java sections) or translate the current version of the 3.0 guide to Spanish.

I am a Mathematician and Computer Scientist who has been working for the last few months writing up the Security Assurance procedures that will be followed in all releases of our products.

Although security is not my main area of expertise, WebApplication development is my main area (especially Java) and therefore I feel that being part of OWASP’s target audience will help me write things in a clear and concise manner that will be easy for developers, architects and executives to understand.

I do not feel that one person can complete the honeycomb project in three months. However, for the given 3-month timeframe (considering my other responsibilities), I would acquire the following commitments:

  • Finish all Java-related articles in the Vulnerabilities section – and others I feel I have the expertise … not sure how many more
  • Organize and sort the articles in the Vulnerabilities and Attacks section
  • Create as many stubs, with basic info, as possible for Vulnerabilities and Attacks section
  • Finish all articles in the “principles” section
  • Finish all articles in the “threats” section
  • Translate all the above to Spanish

if instead OWASP would be more interested in the guide project, I would Translate the 3.0 guide to Spanish

Thank you for your time and consideration.

Please do not hesitate to contact me with any questions or comments.

Best regards,

AoC 3 - Tom

Hi Dinis,

I'm interesting in sorting out the owasp.org website and fixing things up... aka, "WebMaster the Owasp.org website for 3 months and implement all missing functionality". I'm just finishing up my MSc in Information Security at Royal Holloway, University of London. My thesis is on secure coding (investigations into security development lifecycles, how they interact with security assessments and all that lark) however it's not web related so I doubt it'll be useful.



Get back to me.



AoC 4 - Joshua

G'day Dinis,

I have been working with Eoin on the liveCD project and we are hoping to have a Beta version ready for Seattle. I would like to be considered for the "OWASP Autumn of Code" sponsorship.

I have been working very hard in my spare time to get the LiveCD up and running. Basically, I spent some time going through all the distros and testing different build methods. After all the testing Morphix was the easiest and most stable to work with.

So far we have a working version with the following tools installed; WebScarab Nmap Nessus Paros OWASP Guide 2.0 CAL9000 TCPDUmp Ethereal Nikto NetCat

Working on : WebGoat Branding ( Boot Menus, Wallpaper ) KDE Menu Slimming down the build Packaging on CD/DVD Prof. Custom Graphics / Icons RFID Tools VOIP Tools

This project was created because other LiveCD's don't focus on App testing and training. It's mostly infrastructure. That's where "labRat" the Live Distro fills the gap. This is also excellent to have all the OWASP resources during an onsite job or training in the lab. That's where the name came from-- spending those long hours in our security labs.

I'd like to hear your thoughts on the LiveCD project and if you feel it's worthy of sponsorship. I know that several chapter leads I know are anxious to get it up and going.



AoC 5 - Jonathan

My name is Jonathan [...] and I am the Development Security Officer for [...] inc. In my current role I am responsible for the integration of security processes within our companies development lifecycle as well as managing our security engineering team. I have worked in the industry for six years, in which time I was promoted from developer, to architect, and into my current role as DSO.

I have much respect for OWASP and would find this sponsorship program to be an excellent way of getting involved with your organization (of course, the sponsorship money is nice too :). In reviewing the projects listed I have found the 'OWASP Testing Guide' to be the most interesting, but I admit that I have little or no experience with any of the projects. If there any projects you would like to refer me to as an experienced Java developer and understanding my current role, I would be very interested.

Thank you for your time.

AoC 6 - Hardik

Hello Dinis,

I would like to take one of the following projects. But currently i am not aware of exactly what are the remaining things in these projects and what you want to implement. If you can let me know the requirments for following projects then i can take one or multiple projects. I am also having some friends who might be intrested in working on these so we all can work on it. Following is the list of projects we are intrested in:- OWASP WebGoat Project OWASP Validation Project OWASP WebGoat Project - OWASP WebScarab Project If possible please provide me more details or contact of suitable person about the current status and what are the requirments,features needed.

Thanks & Regards,


AoC 7 - Aaron


I would like to submit a project proposal for the OWASP Autumn of Code 2006.

Project Request:

First Choice: WebMaster the Owasp.org website for 3 months and implement all missing functionality

Second Choice: OWASP PHP Project

Third Choice: OWASP AJAX Security Project


I have worked as a professional web developer for 6+ years and have participated in several open source projects including tiki-wiki and other content management system projects. I am employed by the Ontario Libraries as a consultant on web development technologies and web server deployment strategies. During my career, I have had the luxury of learning and furthering my skills through the open-source community of developers who have offered one-on-one advice, project source code, and valuable insight. Without this guidance it would not have been possible for me to progress as quickly as I have, nor would my journey have been as enjoyable of an experience.

My primary interest includes PHP / MySQL development, server administration (FreeBSD / Linux), and graphics design / usability study. As a web developer I have had the opportunity to learn and use numerous technologies and programming languages running under a variety of environments. This has forced me to learn to adapt quickly under various circumstances and environments, and has taught me how to work both alone as well as within a team. I would like to use this unique experience to aid others within the community in any way possible, including the continued development of services within the owasp.org website.

Deliverables (Web Master):

1. Website template and branding 2. Prepare marketing materials (digital format) 3. Content updating and proofing (English) 4. Prepare website documentation for future developers 5. Work in conjunction with other teams (AJAX, JS, PHP) to audit and develop site 6. Develop features and functionality as identified by OWASP and community

Please feel free to contact me at your leisure to discuss my proposal. I will provide a detailed portfolio of my work if this is of interest and/or I can prepare a deliverables list for the other two projects if necessary.

Thank you,

AoC 8 - Josh

Project: Testing Guide

Reasons to be sponsored: It happens to be "be nice to Josh day" today, besides I think I can express the ideas that we want to convey in a clear and readable manner.

Objectives: To deliver a readable and accurate guide on performing an application security review.

I look forward to hearing from you,

AoC 9 - Mike

OWASP Autumn of Code 2006 Application

Project Involvement: I want to work on finishing up SiteGenerator (SG) and OWASP Report Generator (ORG) projects.

Why I Should be Sponsored: I should be sponsored for finishing up SG and ORG because I know I can finish up these projects to a level that the project lead would be satisfied with. I have also been helping out with the OWASP .Net area for the past few years so I already have substantial background knowledge of these projects.


  • Fix errors that are currently in SG and ORG.
  • Create documentation for the programs and publish onto their corresponding wiki pages.
  • Make the SG install process easier by to consolidating the two installers into one.
  • Cleaning up of the code to make it easier for further development.
  • Finishing up the TO-DOs found on https://www.owasp.org/index.php/ORG_%28Owasp_Report_Generator%29.
  • Adding functionality and other items to SG based on the feedback from the project lead.
  • Improve the user interface of the programs.


  • November 15th - I will have most of the common errors fixed in SG and RG, at least 50% of the TO-DOs finished up for both of the programs and a start on the documentation.
  • December 31st - I will have the rest of the functionality, new installers and documentation of the programs on the OWASP wiki.

Through out the process I will be focusing on cleaning up the code for clarity and future modifications as well as improving the user interface.

AoC 10 - Federico


Browsing through the project page, I discovered LAPSE project to which I could make a valuable development contribution in time and skill.

I do not know the project enough to outline specific commitments but I will draft some as soon as I get to know the application a little bit.

Additionally, I currently have access to a full license of WebInspect, which could give us valuable information for the LAPSE project.

Thank you for considering me.

PS, The other documentation project, which I feel I could make a valuable contribution to, is the OWASP Java project.

Best regards,

AoC 11 - Siddharth

Hi Dinis,

I am interested to participate in "OWASP Autumn of Code 2006", So Please loook at the following details.

Contact detail:



I am interested to involve in following project,

  • Write more lessons for WebGoat, integrate it with SiteGenerator and

release it as a product?

Why: I am having about 1 year experience in software industry, and from last 4 months working in web application security.I am very hard working and dedicated to work.

As before 3 month I started learning about web application security, webgoat helped me a lot for practical exposure to pentesting and security review.

I am interested to work for this because I feel it is very useful for trainees and needs the improvements.

OWASP will be very happy to work with person with urge to learn and dedicated to the work.

Objectives and deliverable:

Web goat needs to be improved in the following points:

  • Should add more lessons on ?Analyzing the HTML source? which I feel one of the most important for most of the attacks.
    • Example: Can be used to break functional access control like enabling the controls or functionalities for that user is not authorized by java script.
  • Use of java script in attacks.
  • Should have a lesion on directory indexing hint including guessing the directory names.
  • Lesson to show ? Improper Error Handling? Example: some error showing path of server on the host like, file not found X:\app\app_name\filename

My idea is having 2 main objectives:

  • Make webgoat to cover all possible attacks.
  • To make it useful also for developers. Because today webgoat is concentrating on pentesters. Lessons should have Hints for mitigations and recommendations.

My goal is to make Web Application security popular to developers and get the web secure.


AoC 12 - Pedram

Dear Mr Dinis Cruz,

I am writing in response to the announce posted on Owasp.org for the OWASP Autumn Of Code 2006. I want to involved in "OWASP PHP Project".

Please accept my attached resume as an application for this project. My experience closely fit the posted project description, and I am excited to apply. I have more than 5 years experience in PHP web developing specially secure web developing and more that 10 advisories on PHP web applications (SecurityFocus, Secunia, Security Team).

My ideas for this project:

  • Guide to creating a PHP security class for developers
  • Guide to define variable type, length, format, character set, reasonableness in PHP for input validation
  • Sample secure PHP application (e.g: Secure forms handling, Secure authentication, Secure poll, Secure search, Secure database handling, Secure file handing, ... )

Thank you. Sincerely,

AoC 13 - Rogan



Why I should be sponsored

WebScarab (original) is quite a high profile project within OWASP. I think it is one of the more widely used tools produced by OWASP, with many thousands of downloads over the past few years (more than 6400 of the latest version according to SourceForge).

I believe that I (through my development of WebScarab so far) have demonstrated my commitment to OWASP, as well as my ability to deliver.

Project Details

Classic WebScarab has many flaws, not least of which are usability related ones. WebScarab is hardly intuitive to a newcomer, and there are significant portions of functionality that I suspect only I know how to use properly.

WebScarab-NG was started as a clean-slate implementation of a Web Application Security tool. It is using a modern user interface toolkit (Spring Rich Client), which makes it possible (even easy!) to provide a standards-compliant user interface, that provides immediate "as you type" feedback to the user.

So far, only the proxy functionality has been implemented, and the ability to review conversations. As part of this project, I intend to re-implement the majority of the functions that classic WebScarab provides, so that WebScarab-NG is a compelling alternative to the classic WebScarab.

If you need any additional information, or would like to adjust the scope of this project, please feel free to contact me.



AoC 14 - Eugene

OWASP Autumn of Code 2006 Project Proposal


The OWASP Honeycomb Project

What are the objectives and deliverables:

  • Normalize the CLASP vulnerability taxonomy with Honeycomb categories
  • Help release the Honeycomb User's Guide
  • Article related tasks from the project roadmap:
    • Fill in the contents of the stub Honeycomb articles
    • Refine the content and structure of the Honeycomb articles
    • Eliminate redundancy in the articles and categories
    • Make sure that articles are tagged with appropriate categories

Why you should be sponsored for the project:

I have prior experience with the CLASP and would like to help make the Honeycomb articles more complete and consistent. Overtime Honeycomb has the potential to grow into a very powerful application security resource offering far more benefit than any flat taxonomy could ever provide.

AoC 15 - Alejandro

Hi, Mi name is Alejandro [...], and i'm really interested in participating in OWAP Autumm of Code 2006.

Project of interest: Help to Complete V2.0 of WebScarab and package it as product

Why i should be sponsored ? I have a strong background in Programming, Computer Security and Open Source. I worked several years in a local CA and in the largest bank in Chile, working full on computer security. Also i'm very involved in open source iniciatives, and i'm the co-founder of the first and largest chilean forge (www.chileforge.cl). Also i'm a part-time professor at the Universidad de Chile (one of the two best in Chile), in a Computer Security Diploma. And i really like to program complex stuff :D

What are the objectives and deliverables: In this case i guess that the objetives and deliverables are already clear. If not, i could work in the definition and planning of this project.

Thank you very much


AoC 16 - Rodrigo


  • OWASP Guide Project


  • OWASP Code Review Project


I have a strong background in computer security area, documentation writing and I work as Linux Security Software Engineer.

My dedication will be interesting to the project, because I will use it in my master degree thesis too.


I can work in any of the both projects because I really believe when you write documentation about security pratices you teach how to avoid common mistakes (this mistakes need to be spoted by a code review).

The idea is to write about the common flaws, how it works and can be exploit, evoluting it to more advanced ways to bypass security mechanisms (like advances in sql injection, bypassing char filters, overflowing cgi applications, and so...).

Covered flaws and techniques (all flaws will be explaned with simple samples, that can be performed to everyone to understand how the flaw can be exploited, and seen the real impacts for the application):

  • SQL Injection
  • Cross-site Scripting
  • Buffer Overflows (heap, stack) - CGI programs
  • HTML Injection and client-side vulnerabilities (like many flaws that exist in orkut.com)
  • Many other input validation flaws
  • Cookie and session related problems

The reader will can understand what is the common security flaws that exist in web applications and how it can be exploited (it will give the notion to the developer of the impacts of insecure code).

Also, the reader can easily understand how to audit any web application tool developed, to spot this flaws.

The project will deliver the sections step-by-step, to ensure that readers can easily understand and test the practical samples showed.

Tks in advance,

AoC 17 - Chris

I would like to submit my CAL9000 project for consideration in your OWASP Autumn of Code 2006. I have put a significant amount of time into the project already - over 600 hours. While the tool is useful as-is, I still consider it a proof-of-concept and would like to include functionality that would take it to the next level. Listed below are the upgrades that I guarantee that I would be able to implement by year-end 2006.

XSS Attack Library Page:

  • Allow filtering of attacks based upon what browsers they are effective in.
  • Allow users to create/edit/delete their own attacks that will persist even if the RSnake XSS attack file is updated.
  • Allow display of all user-defined attacks in a print-ready format.
  • Enhance RegEx testing functionality. At a minimum, allow user- defined regex flags and replacement strings. Include show/replace/ split matches and the ability to test the regex against code.

HTTP Requests Page:

  • Give users (near)full control over generating and sending HTTP Requests. (There are some browser-dependent restrictions)
  • Allow users to define HTTP Method Type,Authentication Type w/ values, Schema, FQDN, Port, Absolute path of URL, Parameter, Query String, Request Headers/Body.
  • Allow Quick encoding of an entire request field or selected text (Url, Hex, Unicode, Base64, Md5 encoding types).
  • Allow users to quickly include from a list of Header Names and common Header Values, depending on the Name. (Or use their own)
  • Allow users to quickly include Browser-specific Headers/Values.
  • Allow users to quickly include Method-specific Headers/Values.
  • Allow users to include Request Name/Value pairs and add them to the Query String or the Response Body.
  • All Request/Response results will be saved in persistent History and easily redisplayed.

HTTP Responses Page:

  • Display Target URL, Response Status/Headers/Body.
  • Allow users to view Response Body as it would appear in a browser.
  • Allow users to extract and view Scripts/Forms/Cookies from the response.
  • Allow users to delete Scripts and Forms from Response Body and view the effect on the rendering of the page.
  • Allow display of Request/Response pairs in a print-ready format.

Misc Tools Page:

  • Allow user-defined characters for the String Generator.

Testing Checklist Page

  • Retain the current testing tips and add a testing checklist based on the OWASP Testing Guide. Include the ability for users to create/edit/delete their own checklist items and also create/edit/delete their results/notes for each test.
  • Allow display of all checklist items and results in a print-ready format.

Automater Page:

  • Allow users to create/edit/delete lists of attack strings and define the insertion points in a request. CAL9000 will automatically send a request for each attack string. Results will be available for review in the History. (Basically, this is a scanner where the user gets to define the tests)

Time permitting, I would also like to include some of the functionality of the AttackAPI (http://www.gnucitizen.org/projects/ attackapi/) and add some basic report generating capabilities. However, I can't guarantee these enhancements before year-end, as I haven't had the time yet to spec out what it would take to implement them.

Down the road, I may write a port to Java in order to get away from browser-specific limitations and to give me the ability to include a proxy. However, CAL9000 was created to be a complement to existing scanners and proxy tools, such as WebScarab, so I'm not sure how far I should take it. I am open to any ideas that you may have for future enhancements.

If you have any questions or would like any more information, feel free to contact me.

Thank you,

AoC 18 - Boris

Hi Dinis,

I have just read about the OWASP Autumn Of Code, and I feel rather excited about it! Not every day I do interesting stuff and make some money out of it :)

My name is Boris, and I'm a .NET guy from Belgrade, Serbia. I've been working with .NET (ASP.NET mostly) since its pre-beta days (Microsoft PDC 2000 Orlando pre-release). Lately I become more and more involved with application security domain, and I think I could use some of the knowledge I gained on OWASP Autumn Of Code. I worked on many .NET projects ranging from single-user desktop apps to distributed, BizTalk-based, SWIFT-based financial clearinghouse systems. I worked for Microsoft too :) (that was some time ago, in their Developer & Platform Evangelism group). I'm also a MCSD and MCAD (for .NET), if that matters to you.

So, I like your .NET projects (and overall OWASP goals) very much, and I would be very eager to work on the following item from your "Proejct Ideas" list:

  • Complete all OWASP .Net web tools (ANSA, SAM'SHE, Asp.Net reflector, etc..) and release them as a product

I think it's very important not to neglect security-related issues with the Microsoft Web platform because it's widespread, especially in the enterprise, and with ASP.NET 2.0 (IMHO, its productivity gains are unparalleled today), it will become even more widespread. So, I think that your target market will be very interesting in everything related to MS Web platform, especially because it has been somewhat neglected by security tools authors.

I sincerely hope that this piece of email is just a start :)

Regards, Boris

AoC 19 - thomas

ups - and now its to late, for they closed the owasp automn of code early 9/18th.

i just wanted to ask about participating on owasp's automn of code with checkomatik - a project for managing checks and reports.

checkomatik is based on php/mysql, brings a defined check-template with a handful of predefined texts and checks to a simple webinterface. simple checks like nikto, bannergrabs, whois and so on get handled either by serversniff.net/ (see http://www.serversniff.net/wiki_en/index.php?title=API) or by own functions and scripts.

the goal of the project is to handle and automate the doing, archiving and report of my (somewhat standartized) pen-tests whilst be as flexible as possible e.g. to add additional servers, ips, texts etc. to any check i do.

checks are extensible and completely self-defineable. There is currently an export to pseudo-xml, we are working on odf, rtf and simple html.

I'm using a custom version of checkomatik this since 2 years for my pentests - but i'd need some ressources to refine this for publishing. the code is messy, its not completely multiuser-capable, and its ugly. there is a playground of the actual stage of development at http://serversniff.net/checkomatik

nevermind if its to late anyway,

AoC 20 -

AoC 21 -

AoC 22 -

AoC 23 -

AoC 24 -