OWASP Newsletter 4

Using the same format as used in OWASP Newsletter's 1, 2 and 3 this is the page that will be used for the next Newsletter

OWASP Newsletter #4
Mention Owasp top 10 (and http://sylvanvonstuppe.blogspot.com/2007/01/owasp-top-10-2007-update-rc1.htm), {ask for participation}

mention OWASP brand abuse cases

As normal you can find below the links to the latest WIKI changes (with a new section for 'Interesting Discussion Threads' on our mailing lists)

And don't forget, if you want something to appear in the next version, please add it to OWASP Newsletter 4

Dinis Cruz

Chief OWASP Evangelist

London, UK

OWASP projects that need your help

 * OWASP Top 10 2007 RC1 - We are opening review of the Top 10 2007 until February 28, 2007. Please review the document and provide feedback to the owasp-topten@lists.owasp.org mail list. If you cannot make public submissions or feedback but still wish to make your voice heard, please mail vanderaj (at) owasp.org. Please note: This document is not to be used or referenced until after its release.
 * OWASP Testing Project v2.0 - Now that the The OWASP Testing Guide v2.0 has reached the 'Release Candidate 1 milestone, the time has come to make sure that everything is 100% and that there is nothing major missing (review process ends on the 10th of Feb).
 * Online Questionaires: I (Dinis) want to do a OWASP wide survey, what solution should I use to create, deploy and manage it?
 * WordPress guru needed: Our blogs (http://blogs.owasp.org/) still looks miserable. We need somebody to help Mide de Libero to sort it out (and while you're there get a feed to put on owasp.org and the next version of the OWASP newsletter)
 * This is not from an OWASP project, but a request I received from an MBA Student who is doing a survey on Open Source (http://www.surveymonkey.com/s.asp?u=387523013251])

Featured Project: WebGoat 5.0 RC1
WebGoat Overview

WebGoat is a deliberately insecure J2EE web application maintained by OWASP designed to teach web application security lessons. In each lesson, users must demonstrate their understanding of a security issue by exploiting a real vulnerability in the WebGoat application. For example, in one of the lessons the user must use SQL injection to steal fake credit card numbers. The application is a realistic teaching environment, providing users with hints and code to further explain the lesson.

To get started, read the |WebGoat User and Install Guide

WebGoat 5.0 Release Candidate 1

Thursday January 17th, WebGoat 5.0 Release Candidate 1 was released. Special thanks to the many people who have sent comments and suggestions and those who have put in the effort to contribute their time to this release.

The 5.0 release would not have been possible without the efforts of Sherif Koussa and OWASP Autumn of Code 2006.

This version can be downloaded from OWASP's Sourceforce repository: WebGoat 5.0 RC1

Please send all comments to webgoat AT g2-inc DOT com regarding this release candidate. A final release is scheduled for the end of January

Featured Project: OWASP Documentation Projects
I wrote this on an email the other day, and realized that it was a good list of our best documenation projects:


 * OWASP Top Ten Project "The OWASP Top Ten provides a powerful awareness document for web application security. The OWASP Top Ten represents a broad consensus about what the most critical web application security flaws are. Project members include a variety of security experts from around the world who have shared their expertise to produce this list"
 * OWASP Guide Project "The Guide is aimed at architects, developers, consultants and auditors and is a comprehensive manual for designing, developing and deploying secure web applications."
 * OWASP AppSec FAQ Project "This FAQ answers some of the questions that developers have about Web Application Security. This FAQ is not specific to a particular platform or language. It addresses the common threats to web applications and are applicable to any platform."
 * OWASP Testing Guide "This project's goal is to create a "best practices" penetration testing framework which users can implement in their own organizations and a "low level" penetration testing guide that describes how to find certain issues."
 * OWASP CLASP Project "CLASP (Comprehensive, Lightweight Application Security Process) provides a well-organized and structured approach for moving security concerns into the early stages of the software development lifecycle, whenever possible."
 * OWASP Honeycomb Project "In the Honeycomb project, OWASP is assembling the most comprehensive and integrated guide ever attempted to the fundamental building blocks of application security (principles, threats, attacks, vulnerabilities, and countermeasures) through collaborative community efforts."
 * OWASP Application Security Assessment Standards Project "Currently there is a lack of standardization over what constitutes an application security assessment. With no single set of criteria being referenced, it is suggested that OWASP establish a set of standards defining and establishing a baseline approach to conducting differing types/levels of application security assessment. The standards should be flexible in design to accommodate a range of security assurance levels. The standards should not be viewed as placing requirements on any party. Rather, the standards should make recommendations about what should be done to be consistent with what the OWASP community believes is best practice. Adhering to the standards should help increase end user organization confidence that assessments meet an industry agreed-upon approach.?"
 * OWASP Application Security Metrics Project "This OWASP Project will first identify and provide the OWASP community a set of application security metrics that have been found by contributors to be effective in measuring application security. This will be followed by the development of new metrics that build on the initial metrics foundation to fulfill unmet metrics requirements. The goals of this Project are to make a baseline set of application security metrics available to the OWASP community and subsequently to provide a forum for the community to contribute metrics back into the baseline."
 * OWASP WASS Guide "The WASS, or Web Application Security Standards project, aims at creating a proposed set of minimum requirements a web application must exhibit if it is to be considered "secure". There currently exists a similar set of standard requirements focused at the network level in the Cardholder Information"

New Pages

 * Top 10 2007 - Top 10 2007 RC1 Public Comments & Review page
 * Guide to SQL Injection - Article examining the possibility of tampered SQL query data exploiting your database and/or application.
 * Member Offers - New offers available for all individual OWASP Members and employees of OWASP Corporate Members.
 * Announce:Web Honeynet - Web Honeynet project announcement by SecuriTeam and the ISOTF.
 * Code Auditor Workbench Tool - Ideas about a source code analysis tool to aid security consultants
 * OWASP News 2006, OWASP Community 2006 - These pages contains OWASP news stories and community events from 2006.

Updated pages

 * Membership - Add reference to the Member Offers page and changed the 'Educational Members' category to be 'Educational and Non-Profit Members'
 * Installer details for ORG - Information on how to build an installer for ORG using WiX
 * SQL Injection - Updated with links to the SQL Injection pages in the OWASP Guide, OWASP Code Review and OWASP Testing Guide
 * OWASP Stinger Project‎ - Updated with new release information (2.4 RC1)
 * .Net Research Links - Several new CLR links
 * Fuzzing
 * Testing for SQL Injection, Testing: Information Gathering , Reviewing Code for SQL Injection
 * minor edits or comments: Talk:JAAS Tomcat Login Module, (added link to Orizon Blog) , OWASP Stinger 3 Ideas

New Documents & Presentations from chapters

 * OWASP Testing Guide Presentation
 * OWASP Top 10 2007 RC1.pdf or OWASP Top 10 2007 RC1.doc - the new version of the OWASP Top 10 (Release Candidate 1)
 * From the Belgium chapter:
 * Jan 07:
 * OWASP BE 2007-01-23 OWASP Update.zip - OWASP Update including 2006 poll results
 * [[Image:OWASP BE 2007-01-23 AOP security.zip|OWASP BE 2007-01-23 AOP security.zip]] - AOP Security presentation
 * From the Israel chapter
 * Jan 07
 * of the Universal XSS PDF vulnerability - Cause, Solutions and Fun Stuff
 * Nov 06 (OWASP IL mini conference):
 * Malicious content in enterprise portals
 * Real vs. Virtual Patching
 * "The Core Rule Set": Generic detection of application layer attacks
 * The OWASP Top Ten Backdoors
 * Hacking The Framework
 * Jul 06:
 * Exposing cryptography for software developers
 * Preventing Spoofing, Phishing and Spamming by Secure Usability and Cryptography
 * ValidationQuestionnaire.doc

Latest Blog entries

 * from Life of an OWASP Chapter Leader
 * SDLC for the “Geek”
 * Cross-Chapter cooperation
 * from /dev/sec/webapp
 * Reporting Web Vulns
 * from Security Tales From The .Net Crypt
 * Weird Thing
 * System.Net Logging Tips
 * Great Project About Reflection (.Net not Java)
 * Buffer OverFlow in ILASM and ILDASM
 * from Orizon post
 * XML galore
 * Parsing freedom
 * from Dinis Cruz Blog
 * An example of a flawed XSS BlackList filter

OWASP Community

 * Feb 26-Mar 1 - Black Hat DC
 * OWASP members receive a $100 Briefings discount by inserting BH7DCASSOC in the box marked “Coupon Codes”


 * Feb 22 (18:00h) - London chapter meeting
 * Feb 20 (18:00h) - Rochester chapter meeting
 * Feb 15 (18:00h) - Seattle chapter meeting
 * Feb 15 (18:00h) - Washington DC (MD) chapter meeting
 * Feb 15 (18:00h) - Washington DC (N. VA) chapter meeting
 * Feb 15 (18:00h) - Seattle chapter meeting
 * Feb 14 (18:00h) - Toronto chapter meeting
 * Feb 13 (18:00h) - Ireland chapter meeting
 * Feb 12 (18:30h) - Switzerland chapter meeting
 * Feb 7 (18:30h) - Boston chapter meeting
 * Feb 6-7 - Italy@InfoSecurity
 * Feb 6 (18:00h) - Melbourne chapter meeting
 * Feb 2 (14:00h) - Chennai chapter meeting
 * Jan 31 (15:00h) - Mumbai chapter meeting
 * Jan 30 (11:30h) - Austin chapter meeting

Application Security News

 * Jan 23 - Greasemonkey Backdoor Proof of Concept - A simple Greasemonkey script that illustrates the potential for abuse by hooking a backdoor to your browser using Javascipt and AJAX techniques.


 * Jan 23 - Web Honeynet Project Announcement - The newly formed Web Honeynet Project from SecuriTeam and the ISOTF will in the next few months announce research on real-world web server attacks which infect web servers with: Tools, connect-back shells, bots, downloaders, malware, etc. which are all cross-platform (for web servers) and currently exploited in the wild.

OWASP references in the Media
This week we have two examples of non complience with OWASP brand usage rules, namely ''8. The OWASP Brand must not be used in any materials that could mislead readers by narrowly interpreting a broad application security category. For example, a vendor product that can find or protect against forced browsing must not claim that they address all of the access control category.''


 * Java Source Code Analysis Available for Developers to Improve Software Security and Quality - quote "Java Security Analysis Aligned with OWASP -- KDJ's vulnerability analysis provides excellent coverage of the vulnerabilities from the OWASP Top 10 list."
 * Ounce Labs Simplifies Regulatory and Policy Compliance With New SmartAudit - quote : "1. OWASP Top Ten: Identifies the existence and location in the source code of any of the Top 10 most critical web application security vulnerabilities, a list complied by the Open Web Application Security Project."

The problem with these claims is that it is very hard to know what exactly do they mean. At least in KDJ's case they say "...excelent coverage..." versus Ounce Labs' "...any of the Top 10...".

One idea that is currently being debated is if OWASP brand usage rules should state that if a company makes claims such as the ones above in relation with the OWASP Top 10 (or other OWASP materials), they MUST include a reference to a publicly accessible page that ‘explains’ how well they ‘think’ each element of the Top 10 is covered.