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 AppSec Research 2010 - Stockholm, Sweden"

From OWASP
Jump to: navigation, search
m (Course 2: Introduction to Malware Analysis (two days))
(Conference program + restructured tabs)
Line 15: Line 15:
 
=== Sponsors  ===
 
=== Sponsors  ===
  
Diamond sponsor:<br>
+
Diamond sponsor:<br> [[Image:AppSec Research 2010 Microsoft diamond sponsor.jpg]]  
[[Image:AppSec_Research_2010_Microsoft_diamond_sponsor.jpg]]
 
  
Gold sponsors:<br>
+
Gold sponsors:<br> [[Image:Cybercom logo.png]] [[Image:Portwise logo.png]]<br> [[Image:Fortify logo AppSec Research 2010.png]] [[Image:Omegapoint logo.png]]  
[[Image:Cybercom_logo.png]] [[Image:Portwise logo.png]]<br>
 
[[Image:Fortify_logo_AppSec_Research_2010.png]] [[Image:Omegapoint logo.png]]
 
  
Silver sponsors (3 taken, 5 open):<br>
+
Silver sponsors (3 taken, 5 open):<br> [[Image:Mnemonic logo.png]] [[Image:AppSec Research 2010 sponsor Nixu logo.jpg]] [[Image:AppSec Research 2010 Google 20k sponsor.jpg]]  
[[Image:Mnemonic logo.png]] [[Image:AppSec_Research_2010_sponsor_Nixu_logo.jpg]] [[Image:AppSec_Research_2010_Google_20k_sponsor.jpg]]
 
  
Lunch sponsors (1 taken, 1 open):<br>
+
Lunch sponsors (1 taken, 1 open):<br> [[Image:IIS logo.png]]  
[[Image:IIS logo.png]]  
 
  
Coffee break sponsors (1 taken, 3 open):<br>
+
Coffee break sponsors (1 taken, 3 open):<br> [[Image:MyNethouse logo.png]]  
[[Image:MyNethouse logo.png]]  
 
  
Media sponsors:<br>
+
Media sponsors:<br> [[Image:AppSec Research 2010 Help Net Security sponsor.jpg]]  
[[Image:AppSec_Research_2010_Help_Net_Security_sponsor.jpg]]
 
  
For full sponsoring program see the Sponsoring tab above.
+
For full sponsoring program see the Sponsoring tab above.  
  
 
=== "AppSec Research".equals("AppSec Europe")  ===
 
=== "AppSec Research".equals("AppSec Europe")  ===
Line 52: Line 45:
 
'''Welcome to Stockholm this year!'''<br> Regards, John Wilander  
 
'''Welcome to Stockholm this year!'''<br> Regards, John Wilander  
  
==== Invited Talks ====
+
==== June 21-22 (Training) ====
  
== "Cross-Domain Theft and the Future of Browser Security" ==
+
== Training Registration is now OPEN  ==
[[Image:Appsec_research_2010_invited_talk_1.jpg]]
 
  
'''Chris Evans'''<br>
+
Application security training is given the first two days, '''June 21-22'''. The price is '''€990''' (~$1.350) for a two-day course. Take the chance to learn from the best!
Troublemaker, Information Security Engineer, and Tech Lead at Google inc.<br>
 
Also the sole author of vsftpd.
 
  
'''Ian Fette'''<br>
+
=== Course 1: Threat Modeling and Architecture Review (two days)  ===
Product Manager for Chrome Security and Google's Anti-Malware initiative
 
  
'''Abstract'''<br>
+
[[Image:AppSec Research 2010 Pravir Chandra.jpg]]
The web browser, and associated machinery, is on the front line of attacks. We will first look at design-level problems with the traditional browser in terms of monolithic architecture and fundamental problems with the same-origin policy. We will then look at the types of solution that are starting to appear in browsers such as Google Chrome and Internet Explorer. We will look at other important browser-based defenses such as Safe Browsing. We will detail what a future browser might look like that has a much more secure design, but is still usable on the wide variety of web sites that people use daily.
 
  
== "The Security Development Lifecycle -- The Creation and Evolution of a Security Development Process" ==
+
Pravir Chandra, Fortify Software
  
[[Image:Appsec_research_2010_invited_talk_2.jpg]]
+
'''Abstract''': Threat Modeling and Architecture Review are the cornerstones of a preventative approach to Application Security. By combining these topics into single comprehensive course attendees can get a complete understanding of how to understand the threat an application faces and how the application will handle those potential threats. This enables the risk to be accurately assessed and appropriate changes or mitigating controls recommended.  
  
'''Steve Lipner'''<br>
+
'''Trainer Bio''': Pravir Chandra is Director of Strategic Services at Fortify where he works with clients to build and optimize software security assurance programs. Pravir is widely recognized in the industry for his expertise in software security and code analysis, and also for his ability to apply technical knowledge strategically from a business perspective. His book, Network Security with OpenSSL is a popular reference on protecting software applications through cryptography and secure communications. His varied special project experience includes creating and leading the Open Software Assurance Maturity Model (OpenSAMM) project
Senior Director of Security Engineering Strategy, Trustworthy Computing Security, Microsoft Corporation.<br>
 
Co-author of "The Security Development Lifecycle", Microsoft Press (book cover above).
 
  
'''Abstract'''<br>
+
'''--&gt; [http://guest.cvent.com/i.aspx?4W%2cM3%2c717e8a7c-4453-47ff-addb-721306529534 Register here]'''  
This keynote will review the evolution of the Security Development Lifecycle (SDL) from its origins in the Microsoft “security pushes” of 2002-3 through its current status and application in 2010.  It will emphasize the aspects of change and change management as the SDL and its user community have matured and grown and will conclude with a summary of some recent changes and additions to the SDL.  Specific topics to be addressed include:
 
  
* Motivations for introducing both the SDL and its predecessor processes.
+
=== Course 2: Introduction to Malware Analysis (two days)  ===
* Considerations in selling the process to management and sustaining a mandate over a prolonged period.
 
* Scaling the SDL to an organization with tens of thousands of engineers.
 
* Managing change.
 
* The role of automation in the SDL.
 
* Adaptation of the SDL to agile development processes.
 
* Thoughts for organizations that are considering implementing the SDL.
 
  
The presentation will cover technical aspects of the SDL including a brief review of requirements and tools, and results.
+
[[Image:AppSec Research 2010 Jason Geffner.jpg]]
  
'''Speaker Bio'''<br>
+
Jason Geffner, Next Generation Security Software (NGS), and Scott Lambert, Microsoft  
Steven B. Lipner is senior director of Security Engineering Strategy at Microsoft Corp where he is responsible for programs that provide improved product security for Microsoft customers. Lipner leads Microsoft’s Security Development Lifecycle (SDL) team and is responsible for the definition of Microsoft’s SDL and for programs to make the SDL available to organizations beyond Microsoft.  Lipner is also responsible for Microsoft’s corporate strategies related to government security evaluation of Microsoft products. 
 
Lipner joined Microsoft in 1999 and was initially responsible for the Microsoft Security Response Center.  In the aftermath of the major computer “worm” incidents of 2001, Lipner and his team formulated and led programs that helped customers respond to the immediate challenges posed by software vulnerabilities and Internet worms.  Lipner and his team also devised the strategy of “security pushes” that, as part of the Trustworthy Computing initiative, enabled Microsoft to make rapid improvements in the security of its software products and to change the corporate development culture to emphasize product security.  The SDL is the product of these improvements, and is widely viewed as the industry’s leading secure software development process.
 
  
Before joining Microsoft, Lipner worked for a variety of software vendors and government contractors as a researcher, consultant, development manager and general manager in IT security. Many of the concepts whose development he led form the basis for today’s approaches to building secure systems. Some examples of these contributions include the application of virtual machine monitors (VMMs) as an approach to isolating security domains, and mathematical models for multilevel security.
+
'''Abstract''': Security researchers are facing a growing problem in the complexity of malicious executables. While dynamic black-box automation tools exist to discover what malware will do on a given execution, it is often important for an analyst to know the full capabilities of a given malware sample. What port does it listen on? What password does it expect for backdoor access? What files will it write to? What will it do tomorrow that it didn't do today? This class will focus on teaching attendees the steps required to understand the functionality of given malware samples. This is a hands-on course. Attendees will work on real-world malware through a series of lab exercises designed to build their expertise in understanding the analysis process.  
  
Lipner is coauthor with Michael Howard of The Security Development Lifecycle (Microsoft Press, 2006) and is named as inventor on twelve U.S. patents and two pending applications in the field of computer and network security.  He has authored numerous professional papers and conference presentations, and served on several National Research Council committees.  He served two terms – a total of more than ten years – on the United States Information Security and Privacy Advisory Board and its predecessor. Lipner holds S.B. and S.M. degrees in Civil Engineering from the Massachusetts Institute of Technology and attended the Harvard Business School’s Program for Management Development. 
+
Learning Objectives:
  
==== Training  ====
+
*An understanding of how to use reverse engineering tools
 +
*An understanding of low-level code and data flow
 +
*PE File format
 +
*x86 Assembly language
 +
*API functions often used by malware
 +
*Anti-analysis tricks and how to defeat them
 +
*Exploits and Shellcode
 +
*A methodology for analyzing malware with and without the use of specialized tools
  
== Training Registration is now OPEN ==
+
'''Trainer Bio''': Jason Geffner joined Next Generation Security Software Ltd. in June of 2007 as a Principal Security Consultant. Jason focuses on performing security reviews of source code and designs, reverse engineering software protection methods and DRM protection methods, deobfuscating and analyzing malware, penetration testing web applications and network infrastructures, and developing automated security analysis tools.
  
Application security training is given the first two days, '''June 21-22'''. The price is '''€990''' (~$1.350) for a two-day course. Take the chance to learn from the best!
+
'''--&gt; [http://guest.cvent.com/i.aspx?4W%2cM3%2c717e8a7c-4453-47ff-addb-721306529534 Register here]'''  
  
=== Course 1: Threat Modeling and Architecture Review (two days) ===
+
=== Course 3: Building Secure Ajax and Web 2.0 Applications (two days) ===
[[Image:AppSec_Research_2010_Pravir_Chandra.jpg]]
 
  
Pravir Chandra, Fortify Software
+
[[Image:AppSec Research 2010 Dave Wichers.jpg]]
  
'''Abstract''': Threat Modeling and Architecture Review are the cornerstones of a preventative approach to Application Security. By combining these topics into single comprehensive course attendees can get a complete understanding of how to understand the threat an application faces and how the application will handle those potential threats. This enables the risk to be accurately assessed and appropriate changes or mitigating controls recommended.
+
Dave Wichers, Aspect Security  
  
'''Trainer Bio''': Pravir Chandra is Director of Strategic Services at Fortify where he works with clients to build and optimize software security assurance programs. Pravir is widely recognized in the industry for his expertise in software security and code analysis, and also for his ability to apply technical knowledge strategically from a business perspective. His book, Network Security with OpenSSL is a popular reference on protecting software applications through cryptography and secure communications. His varied special project experience includes creating and leading the Open Software Assurance Maturity Model (OpenSAMM) project
+
'''Abstract''': Students gain hands-on testing experience with freely available web application security test tools to find and diagnose flaws and learn how to identify them in their own projects. Because finding flaws is worthless without effective communication, the course also covers the process of creating and communicating software security flaws effectively. In addition, Aspect’s engineers are leaders in the AppSec Community and will offer the students an amazing perspective.  
  
'''--> [http://guest.cvent.com/i.aspx?4W%2cM3%2c717e8a7c-4453-47ff-addb-721306529534 Register here]'''
+
From the course outline:<br> CSS Attacks, Browser Add On Attacks, RSS / Data Feed Attacks, Microsoft Active X, Adobe Flash/Flex/AIR, Silverlight, Java FX, Ajax Mashups, Same Origin Policy, JavaScript, Web 2.0 CSRF Attacks, XHR JSON Forgery, Best Practice: Check HTTP Headers, Best Practice: Unique ID For XHR, JSON and XML Based XSS, How to use OWASP AntiSamy, Blended Threats, Dealing with Ajax Toolkits, Best Practice: Fuzzing ...  
  
=== Course 2: Introduction to Malware Analysis (two days) ===
+
'''Trainer Bio''': Dave Wichers is a member of the OWASP Board and a coauthor, along with Jeff Williams, of all previous versions of the OWASP Top Ten. Dave is also the Chief Operating Officer of Aspect Security, a company that specializes in application security services. Mr. Wichers brings over twenty years of experience in the information security field. Prior to cofounding Aspect, he ran the Application Security Services Group at a large data center company, Exodus Communications. His current work involves helping customers, from small e-commerce sites to Fortune 500 corporations and the U.S. Government, secure their applications by providing application security design, architecture, and SDLC support services: including code review, application penetration testing, security policy development, security consulting services, and developer training.  
[[Image:AppSec_Research_2010_Jason_Geffner.jpg]]
 
  
Jason Geffner, Next Generation Security Software (NGS), and Scott Lambert, Microsoft
+
'''--&gt; [http://guest.cvent.com/i.aspx?4W%2cM3%2c717e8a7c-4453-47ff-addb-721306529534 Register here]'''
  
'''Abstract''': Security researchers are facing a growing problem in the complexity of malicious executables. While dynamic black-box automation tools exist to discover what malware will do on a given execution, it is often important for an analyst to know the full capabilities of a given malware sample. What port does it listen on? What password does it expect for backdoor access? What files will it write to? What will it do tomorrow that it didn't do today? This class will focus on teaching attendees the steps required to understand the functionality of given malware samples. This is a hands-on course. Attendees will work on real-world malware through a series of lab exercises designed to build their expertise in understanding the analysis process.
+
=== Course 4: Assessing and Exploiting Web Apps with Samurai-WTF (two days)  ===
  
Learning Objectives:
+
[[Image:AppSec Research 2010 Justin Searle.jpg]]
* An understanding of how to use reverse engineering tools
 
* An understanding of low-level code and data flow
 
* PE File format
 
* x86 Assembly language
 
* API functions often used by malware
 
* Anti-analysis tricks and how to defeat them
 
* Exploits and Shellcode
 
* A methodology for analyzing malware with and without the use of specialized tools
 
  
'''Trainer Bio''': Jason Geffner joined Next Generation Security Software Ltd. in June of 2007 as a Principal Security Consultant. Jason focuses on performing security reviews of source code and designs, reverse engineering software protection methods and DRM protection methods, deobfuscating and analyzing malware, penetration testing web applications and network infrastructures, and developing automated security analysis tools.
+
Justin Searle, InGuardians
  
'''--> [http://guest.cvent.com/i.aspx?4W%2cM3%2c717e8a7c-4453-47ff-addb-721306529534 Register here]'''
+
'''Abstract''': This course will focus on using open source tools to perform web application assessments. The course will take attendees through the process of application assessment using the open source tools included in the Samurai Web Testing Framework Live CD (Samurai-WTF). Day one will take students through the steps and open source tools used to assess applications for vulnerabilities. Day two will focus on the exploitation of web app vulnerabilities, spending half the day on server side attacks and the other half of the day on client side attacks. The latest tools and techniques will be use throughout the course, including several tools developed by the trainers themselves.  
  
=== Course 3: Building Secure Ajax and Web 2.0 Applications (two days) ===
+
'''Trainer Bio''': Justin Searle, a Senior Security Analyst with InGuardians, specializes in web application, network, and embedded penetration testing. Justin has presented at top security conferences including DEFCON, ToorCon, ShmooCon, and SANS. Justin has an MBA in International Technology and is CISSP and SANS GIAC-certified in incident handling and hacker techniques (GCIH) and intrusion analysis (GCIA). Justin is one of the founders and lead developers of Samurai-WTF.  
[[Image:AppSec_Research_2010_Dave_Wichers.jpg]]
 
  
Dave Wichers, Aspect Security
+
'''--&gt; [http://guest.cvent.com/i.aspx?4W%2cM3%2c717e8a7c-4453-47ff-addb-721306529534 Register here]'''
  
'''Abstract''': Students gain hands-on testing experience with freely available web application security test tools to find and diagnose flaws and learn how to identify them in their own projects. Because finding flaws is worthless without effective communication, the course also covers the process of creating and communicating software security flaws effectively. In addition, Aspect’s engineers are leaders in the AppSec Community and will offer the students an amazing perspective.
+
=== Course 5: Securing Web Services (two days)  ===
  
From the course outline:<br>
+
[[Image:AppSec Research 2010 Jason Li.jpg]]
CSS Attacks, Browser Add On Attacks, RSS / Data Feed Attacks, Microsoft Active X, Adobe Flash/Flex/AIR, Silverlight, Java FX, Ajax Mashups, Same Origin Policy, JavaScript, Web 2.0 CSRF Attacks, XHR JSON Forgery, Best Practice: Check HTTP Headers, Best Practice: Unique ID For XHR, JSON and XML Based XSS, How to use OWASP AntiSamy, Blended Threats, Dealing with Ajax Toolkits, Best Practice: Fuzzing ...
 
  
'''Trainer Bio''': Dave Wichers is a member of the OWASP Board and a coauthor, along with Jeff Williams, of all previous versions of the OWASP Top Ten. Dave is also the Chief Operating Officer of Aspect Security, a company that specializes in application security services. Mr. Wichers brings over twenty years of experience in the information security field. Prior to cofounding Aspect, he ran the Application Security Services Group at a large data center company, Exodus Communications. His current work involves helping customers, from small e-commerce sites to Fortune 500 corporations and the U.S. Government, secure their applications by providing application security design, architecture, and SDLC support services: including code review, application penetration testing, security policy development, security consulting services, and developer training.
+
Jason Li, Aspect Security  
  
'''--> [http://guest.cvent.com/i.aspx?4W%2cM3%2c717e8a7c-4453-47ff-addb-721306529534 Register here]'''
+
'''Abstract''': Aspect Security offers a one or two day course titled Securing Web Services designed to focus on the most important messages regarding the development and of secure web services. The objective for this course is to ensure that developers understand the real risks associated with Service Oriented Architectures, what standard are available to help, and how to use the standards. The course includes a combination of lecture and demonstration designed to provide detailed guidance regarding the implementation of specific security principles and functions.  
  
=== Course 4: Assessing and Exploiting Web Apps with Samurai-WTF (two days) ===
+
'''Trainer Bio''': Jason Li is a Senior Application Security Engineer for Aspect Security where he performs application security assessments and architecture reviews, as well as application security training, to a wide variety of financial and government customers. Jason is an active OWASP leader, contributing to several OWASP projects and serving on the OWASP Global Projects Committee. He holds a Post-Masters certificate in Computer Science and concentration in Information Security from Johns Hopkins University and a Masters degree in Computer Science from Cornell University.  
[[Image:AppSec_Research_2010_Justin_Searle.jpg]]
 
  
Justin Searle, InGuardians
+
'''--&gt; [http://guest.cvent.com/i.aspx?4W%2cM3%2c717e8a7c-4453-47ff-addb-721306529534 Register here]'''
  
'''Abstract''': This course will focus on using open source tools to perform web application assessments. The course will take attendees through the process of application assessment using the open source tools included in the Samurai Web Testing Framework Live CD (Samurai-WTF).  Day one will take students through the steps and open source tools used to assess applications for vulnerabilities.  Day two will focus on the exploitation of web app vulnerabilities, spending half the day on server side attacks and the other half of the day on client side attacks.  The latest tools and techniques will be use throughout the course, including several tools developed by the trainers themselves.
+
==== June 23 ====
  
'''Trainer Bio''': Justin Searle, a Senior Security Analyst with InGuardians, specializes in web application, network, and embedded penetration testing.  Justin has presented at top security conferences including DEFCON, ToorCon, ShmooCon, and SANS.  Justin has an MBA in International Technology and is CISSP and SANS GIAC-certified in incident handling and hacker techniques (GCIH) and intrusion analysis (GCIA). Justin is one of the founders and lead developers of Samurai-WTF.
+
{| border="0" align="center" style="width: 80%;"
 +
|-
 +
! align="center" colspan="4" style="background: none repeat scroll 0% 0% rgb(64, 88, 160); color: white;" | Conference Day 1 - June 23, 2010
 +
|-
 +
| style="width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);" | <br>
 +
| style="width: 30%; background: none repeat scroll 0% 0% rgb(188, 133, 122);" | Track 1
 +
| style="width: 30%; background: none repeat scroll 0% 0% rgb(188, 165, 122);" | Track 2
 +
| style="width: 30%; background: none repeat scroll 0% 0% rgb(153, 255, 153);" | Track 3
 +
|-
 +
| style="width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);" | 08:00-08:50
 +
| align="left" colspan="3" style="width: 80%; background: none repeat scroll 0% 0% rgb(194, 194, 194);" | Registration and Coffee
 +
|-
 +
| style="width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);" | 08:50-09:00
 +
| align="center" colspan="3" style="width: 80%; background: none repeat scroll 0% 0% rgb(242, 242, 242);" | Welcome to OWASP AppSec Research 2010 Conference
 +
''John Wilander, OWASP Sweden &amp; Dave Wichers, OWASP Foundation''
  
'''--> [http://guest.cvent.com/i.aspx?4W%2cM3%2c717e8a7c-4453-47ff-addb-721306529534 Register here]'''
+
|-
 +
| style="width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);" | 09:00-10:00
 +
| align="center" colspan="3" style="width: 80%; background: none repeat scroll 0% 0% rgb(242, 242, 242);" | Cross-Domain Theft and the Future of Browser Security
 +
''Chris Evans, Information Security Engineer, and Ian Fette, Product Manager for Chrome Security, Google''  
  
=== Course 5: Securing Web Services (two days) ===
+
|-
[[Image:AppSec_Research_2010_Jason_Li.jpg]]
+
| style="width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);" | 10:10-10:45
 +
| align="left" style="width: 30%; background: none repeat scroll 0% 0% rgb(188, 133, 122);" | BitFlip: Determine a Data's Signature Coverage from within the Application
 +
''Henrich Christopher Poehls''<br>
  
Jason Li, Aspect Security
+
| align="left" style="width: 30%; background: none repeat scroll 0% 0% rgb(188, 165, 122);" | CsFire:&nbsp;Browser Enforced Mitigation Against CSRF
 +
''Lieven&nbsp;Desmet&nbsp;and&nbsp;Philippe&nbsp;De&nbsp;Ryck''<br>
  
'''Abstract''': Aspect Security offers a one or two day course titled Securing Web Services designed to focus on the most important messages regarding the development and of secure web services. The objective for this course is to ensure that developers understand the real risks associated with Service Oriented Architectures, what standard are available to help, and how to use the standards.  The course includes a combination of lecture and demonstration designed to provide detailed guidance regarding the implementation of specific security principles and functions.
+
| align="left" style="width: 30%; background: none repeat scroll 0% 0% rgb(153, 255, 153);" | Deconstructing ColdFusion
 +
''Chris Eng''  
  
'''Trainer Bio''': Jason Li is a Senior Application Security Engineer for Aspect Security where he performs application security assessments and architecture reviews, as well as application security training, to a wide variety of financial and government customers. Jason is an active OWASP leader, contributing to several OWASP projects and serving on the OWASP Global Projects Committee. He holds a Post-Masters certificate in Computer Science and concentration in Information Security from Johns Hopkins University and a Masters degree in Computer Science from Cornell University.
+
|-
 +
| style="width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);" | 10:45-11:10
 +
| align="left" colspan="2" style="width: 90%; background: none repeat scroll 0% 0% rgb(194, 194, 194);" | Break - Expo
 +
| align="left" style="width: 30%; background: none repeat scroll 0% 0% rgb(153, 255, 153);" | CTF Kick-Off
 +
<br>
 +
 
 +
|-
 +
| style="width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);" | 11:10-11:45
 +
| align="left" style="width: 30%; background: none repeat scroll 0% 0% rgb(188, 133, 122);" | Towards Building Secure Web Mashups
 +
''Wouter Joosen''
 +
 
 +
| align="left" style="width: 30%; background: none repeat scroll 0% 0% rgb(188, 165, 122);" | Automated vs. Manual Security:&nbsp;You Can't Filter The Stupid<br>
 +
''David Byrne and Charles Henderson''
 +
 
 +
| align="left" style="width: 30%; background: none repeat scroll 0% 0% rgb(153, 255, 153);" | How to Render SSL&nbsp;Useless
 +
''Ivan Ristic''
 +
 
 +
|-
 +
| style="width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);" | 11:55-12:30
 +
| align="left" style="width: 30%; background: none repeat scroll 0% 0% rgb(188, 133, 122);" |
 +
Enterprise security patterns for RESTful Web Services
 +
 
 +
''Francois Lascelles''<br>
 +
 
 +
| align="left" style="width: 30%; background: none repeat scroll 0% 0% rgb(188, 165, 122);" | Web Frameworks and How They Kill Traditional Security Scanning
 +
''Christian Hang''
 +
 
 +
| align="left" style="width: 30%; background: none repeat scroll 0% 0% rgb(153, 255, 153);" | The State of SSL&nbsp;in the World
 +
''Michael Boman''
 +
 
 +
|-
 +
| style="width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);" | 12:30-13:45
 +
| align="left" colspan="3" style="width: 80%; background: none repeat scroll 0% 0% rgb(194, 194, 194);" | Lunch - Expo - CTF
 +
|-
 +
| style="width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);" | 13:45-14:20
 +
| align="left" style="width: 30%; background: none repeat scroll 0% 0% rgb(188, 133, 122);" | Securing Web Applications with ESAPI
 +
''Ken Sipe''
 +
 
 +
| align="left" style="width: 30%; background: none repeat scroll 0% 0% rgb(188, 165, 122);" | Beyond the Same Origin Policy
 +
''Jasvir Nagra and Mike Samuel''
 +
 
 +
| align="left" style="width: 30%; background: none repeat scroll 0% 0% rgb(153, 255, 153);" | SymFileFuzzer - a New File Fuzzer Tool
 +
''Komal Randive''
 +
 
 +
|-
 +
| style="width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);" | 14:30-15:05
 +
| align="left" style="width: 30%; background: none repeat scroll 0% 0% rgb(188, 133, 122);" | Security Toolbox for .NET&nbsp;Development and Testing
 +
''Johan Lindfors and Dag König''
 +
 
 +
| align="left" style="width: 30%; background: none repeat scroll 0% 0% rgb(188, 165, 122);" | Cross-Site Location Jacking (XSLJ) (not really)
 +
''David Lindsay and Eduardo Vela Nava''
 +
 
 +
| align="left" style="width: 30%; background: none repeat scroll 0% 0% rgb(153, 255, 153);" | Owning Oracle:&nbsp;Sessions and Credentials
 +
''Wendel G. Henrique and Steve Ocepek''
 +
 
 +
|-
 +
| style="width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);" | 15:05-15:30
 +
| align="left" colspan="3" style="width: 80%; background: none repeat scroll 0% 0% rgb(194, 194, 194);" | Break - Expo - CTF
 +
|-
 +
| style="width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);" | 15:30-16:05
 +
| align="left" style="width: 30%; background: none repeat scroll 0% 0% rgb(188, 133, 122);" | Value Objects a la Doman-Driven Security:&nbsp;A&nbsp;Design Mindset to Avoid SQL&nbsp;Injection and Cross-Site Scripting Vulnerabilities
 +
''Dan Bergh Johnsson''
 +
 
 +
| align="left" style="width: 30%; background: none repeat scroll 0% 0% rgb(188, 165, 122);" | New Insights into Clickjacking
 +
''Marco Balduzzi''  
 +
 
 +
| align="left" style="width: 30%; background: none repeat scroll 0% 0% rgb(153, 255, 153);" | Session Fixation - the Forgotten Vulnerability?
 +
''Michael Schrank, Bastian Braun and Martin Johns''
 +
 
 +
|-
 +
| style="width: 10%; background: none repeat scroll 0% 0% rgb(123, 138, 189);" | 16:15-17:00
 +
| align="center" colspan="3" style="width: 90%; background: none repeat scroll 0% 0% rgb(242, 242, 242);" | Panel Discussion: To Be Announced
 +
|}
 +
 
 +
==== June 24  ====
 +
 
 +
{| style="width:80%" border="0" align="center"
 +
|-
 +
! colspan="4" align="center" style="background:#4058A0; color:white" | Conference Day 2 - June 23, 2010
 +
|-
 +
| style="width:10%; background:#7B8ABD" |
 +
| style="width:30%; background:#BC857A" | Track 1
 +
| style="width:30%; background:#BCA57A" | Track 2
 +
| style="width:30%; background:#99FF99" | Track 3
 +
|-
 +
| style="width:10%; background:#7B8ABD" | 09:00-10:00
 +
| colspan="3" style="width:80%; background:#F2F2F2" align="center" | The Security Development Lifecycle -- The Creation and Evolution of a Security Development Process<br>Steve Lipner, Senior Director of Security Engineering Strategy, Microsoft Corporation
 +
|-
 +
| style="width:10%; background:#7B8ABD" | 10:10-10:45
 +
| style="width:30%; background:#BC857A" align="left" |
 +
Building Security In Maturity Model: A Review of Successful Software Security Programs in Europe
 +
 
 +
''Gabriele Giuseppini and Terri Randolph''
 +
 
 +
| style="width:30%; background:#BCA57A" align="left" |
 +
Promon TestSuite -- Client Based Penetration Testing Tool
 +
 
 +
''Folker den Braber and Tom Lysemose Hansen''
 +
 
 +
| style="width:30%; background:#99FF99" align="left" |
 +
A Taint Mode for Python via a Library<br>2.0
 +
 
 +
''Juan José Conti and Alejandro Russo''
 +
 
 +
|-
 +
| style="width:10%; background:#7B8ABD" | 10:45-11:10
 +
| colspan="3" style="width:90%; background:#C2C2C2" align="left" | Break - Expo - CTF
 +
|-
 +
| style="width:10%; background:#7B8ABD" | 11:10-11:45
 +
| style="width:30%; background:#BC857A" align="left" |
 +
Microsoft's Security Development Lifecycle for Agile Development
 +
 
 +
''Nick Coblentz''
 +
 
 +
| style="width:30%; background:#BCA57A" align="left" |
 +
Detecting and Protecting You Users from 100% of all Malware -- How?
 +
 
 +
''Bradley Anstis and Ellynora Nicoll''
 +
 
 +
| style="width:30%; background:#99FF99" align="left" |
 +
OPA: Language Support for a Sane, Safe and Secure Web
 +
 
 +
''David Rajchenbach-Teller and François-Régis Sinot''
 +
 
 +
|-
 +
| style="width:10%; background:#7B8ABD" | 11:55-12:30
 +
| style="width:30%; background:#BC857A" align="left" |
 +
Secure Application Development for the Enterprise: Practical, Real-World Tips
 +
 
 +
''Michael Craigue''
 +
 
 +
| style="width:30%; background:#BCA57A" align="left" |
 +
Responsibility for the Harm and Risk of Software Security Flaws
 +
 
 +
''Cassio Goldschmidt''
 +
 
 +
| style="width:30%; background:#99FF99" align="left" |
 +
Secure the Clones: Static Enforcement of Policies for Secure Object Copying
 +
 
 +
''Thomas Jensen and David Pichardie''
 +
 
 +
|-
 +
| style="width:10%; background:#7B8ABD" | 12:30-13:45
 +
| colspan="3" style="width:80%; background:#C2C2C2" align="left" | Lunch - Expo - CTF
 +
|-
 +
| style="width:10%; background:#7B8ABD" | 13:45-14:20
 +
| style="width:30%; background:#BC857A" align="left" |
 +
Product Security Management in Agile Product Management
 +
 
 +
''Antti Vähä-Sipilä''
 +
 
 +
| style="width:30%; background:#BCA57A" align="left" |
 +
Hacking by Numbers
 +
 
 +
''Tom Brennan<br>''
 +
 
 +
| style="width:30%; background:#99FF99" align="left" |
 +
Safe Wrappers and Sane Policies for Self Protecting JavaScript
 +
 
 +
''Jonas Magazinius, Phu H. Phung and David Sands''
 +
 
 +
|-
 +
| style="width:10%; background:#7B8ABD" | 14:30-15:05
 +
| style="width:30%; background:#BC857A" align="left" |
 +
OWASP Top 10 2010
 +
 
 +
''Dave Wichers<br>''
 +
 
 +
| style="width:30%; background:#BCA57A" align="left" |
 +
Application Security Scoreboard in the Sky
 +
 
 +
''Chris Eng''
 +
 
 +
| style="width:30%; background:#99FF99" align="left" |
 +
On the Privacy of File Sharing Services
 +
 
 +
''Nick Nikiforakis, Francesco Gadaleta, Yves Younan, and Wouter Joosen''
 +
 
 +
|-
 +
| style="width:10%; background:#7B8ABD" | 15:05-15:30
 +
| colspan="3" style="width:80%; background:#C2C2C2" align="left" | Break - Expo - CTF
 +
|-
 +
| style="width:10%; background:#7B8ABD" | 15:30-16:00
 +
| colspan="3" style="width:90%; background:#F2F2F2" align="center" | CTF Price Ceremony, Announcement of OWASP AppSec EU 2011, Closing Notes
 +
|}
 +
 
 +
==== Invited Talks  ====
 +
 
 +
== "Cross-Domain Theft and the Future of Browser Security"  ==
 +
 
 +
[[Image:Appsec research 2010 invited talk 1.jpg]]
 +
 
 +
'''Chris Evans'''<br> Troublemaker, Information Security Engineer, and Tech Lead at Google inc.<br> Also the sole author of vsftpd.
 +
 
 +
'''Ian Fette'''<br> Product Manager for Chrome Security and Google's Anti-Malware initiative
 +
 
 +
'''Abstract'''<br> The web browser, and associated machinery, is on the front line of attacks. We will first look at design-level problems with the traditional browser in terms of monolithic architecture and fundamental problems with the same-origin policy. We will then look at the types of solution that are starting to appear in browsers such as Google Chrome and Internet Explorer. We will look at other important browser-based defenses such as Safe Browsing. We will detail what a future browser might look like that has a much more secure design, but is still usable on the wide variety of web sites that people use daily.
 +
 
 +
== "The Security Development Lifecycle -- The Creation and Evolution of a Security Development Process"  ==
 +
 
 +
[[Image:Appsec research 2010 invited talk 2.jpg]]
 +
 
 +
'''Steve Lipner'''<br> Senior Director of Security Engineering Strategy, Trustworthy Computing Security, Microsoft Corporation.<br> Co-author of "The Security Development Lifecycle", Microsoft Press (book cover above).
 +
 
 +
'''Abstract'''<br> This keynote will review the evolution of the Security Development Lifecycle (SDL) from its origins in the Microsoft “security pushes” of 2002-3 through its current status and application in 2010. It will emphasize the aspects of change and change management as the SDL and its user community have matured and grown and will conclude with a summary of some recent changes and additions to the SDL. Specific topics to be addressed include:
 +
 
 +
*Motivations for introducing both the SDL and its predecessor processes.
 +
*Considerations in selling the process to management and sustaining a mandate over a prolonged period.
 +
*Scaling the SDL to an organization with tens of thousands of engineers.
 +
*Managing change.
 +
*The role of automation in the SDL.
 +
*Adaptation of the SDL to agile development processes.
 +
*Thoughts for organizations that are considering implementing the SDL.
 +
 
 +
The presentation will cover technical aspects of the SDL including a brief review of requirements and tools, and results.
 +
 
 +
'''Speaker Bio'''<br> Steven B. Lipner is senior director of Security Engineering Strategy at Microsoft Corp where he is responsible for programs that provide improved product security for Microsoft customers. Lipner leads Microsoft’s Security Development Lifecycle (SDL) team and is responsible for the definition of Microsoft’s SDL and for programs to make the SDL available to organizations beyond Microsoft. Lipner is also responsible for Microsoft’s corporate strategies related to government security evaluation of Microsoft products. Lipner joined Microsoft in 1999 and was initially responsible for the Microsoft Security Response Center. In the aftermath of the major computer “worm” incidents of 2001, Lipner and his team formulated and led programs that helped customers respond to the immediate challenges posed by software vulnerabilities and Internet worms. Lipner and his team also devised the strategy of “security pushes” that, as part of the Trustworthy Computing initiative, enabled Microsoft to make rapid improvements in the security of its software products and to change the corporate development culture to emphasize product security. The SDL is the product of these improvements, and is widely viewed as the industry’s leading secure software development process.
 +
 
 +
Before joining Microsoft, Lipner worked for a variety of software vendors and government contractors as a researcher, consultant, development manager and general manager in IT security. Many of the concepts whose development he led form the basis for today’s approaches to building secure systems. Some examples of these contributions include the application of virtual machine monitors (VMMs) as an approach to isolating security domains, and mathematical models for multilevel security.  
  
'''--> [http://guest.cvent.com/i.aspx?4W%2cM3%2c717e8a7c-4453-47ff-addb-721306529534 Register here]'''
+
Lipner is coauthor with Michael Howard of The Security Development Lifecycle (Microsoft Press, 2006) and is named as inventor on twelve U.S. patents and two pending applications in the field of computer and network security. He has authored numerous professional papers and conference presentations, and served on several National Research Council committees. He served two terms – a total of more than ten years – on the United States Information Security and Privacy Advisory Board and its predecessor. Lipner holds S.B. and S.M. degrees in Civil Engineering from the Massachusetts Institute of Technology and attended the Harvard Business School’s Program for Management Development.  
  
 
==== Registration  ====
 
==== Registration  ====
  
==Registration is now OPEN==
+
== Registration is now OPEN ==
  
'''[http://guest.cvent.com/i.aspx?4W%2cM3%2c717e8a7c-4453-47ff-addb-721306529534 Click Here To Register]'''
+
'''[http://guest.cvent.com/i.aspx?4W%2cM3%2c717e8a7c-4453-47ff-addb-721306529534 Click Here To Register]'''  
  
Note: To save on processing expenses, all fees paid for the OWASP conference are non-refundable. OWASP can accommodate transfers of registrations from one person to another, if such an adjustment becomes necessary.
+
Note: To save on processing expenses, all fees paid for the OWASP conference are non-refundable. OWASP can accommodate transfers of registrations from one person to another, if such an adjustment becomes necessary.  
  
== Stay Informed ... and Tell Others ==
+
== Stay Informed ... and Tell Others ==
[https://lists.owasp.org/mailman/listinfo/appsec_eu_2010 Subscribe to the conference '''mailing list''']. This is the official information channel and you'll be the first to know about the program, invited speakers, opening of registration for training etc.
 
  
[http://events.linkedin.com/OWASP-AppSec-Research-2010/pub/185990 Add the event to your '''LinkedIn''' profle] to tell all your business contacts that AppSec Research 2010 is the place to be.
+
[https://lists.owasp.org/mailman/listinfo/appsec_eu_2010 Subscribe to the conference '''mailing list''']. This is the official information channel and you'll be the first to know about the program, invited speakers, opening of registration for training etc.  
  
Then get on the '''Twitter''' stream by using the tags '''#OWASP''' and '''#AppSecEU'''.
+
[http://events.linkedin.com/OWASP-AppSec-Research-2010/pub/185990 Add the event to your '''LinkedIn''' profle] to tell all your business contacts that AppSec Research 2010 is the place to be.  
  
== Conference Fees ==
+
Then get on the '''Twitter''' stream by using the tags '''#OWASP''' and '''#AppSecEU'''.
* Early Bird registration, February 7 - April 7: €300
 
* Regular registration, April 8 and onwards: €350
 
* OWASP individual members (not just chapter member): €300
 
* Full-time students*: €225
 
  
* Training fee is €990 for two days, see Training tab above
+
== Conference Fees  ==
  
<nowiki>*</nowiki> We need some kind of proof of your full-time student status. Either ask your local OWASP chapter leader to vouch for you by email to [email protected], or email Kate a scanned image of your student ID (please compress the file size :).
+
*Early Bird registration, February 7 - April 7: €300
 +
*Regular registration, April 8 and onwards: €350
 +
*OWASP individual members (not just chapter member): €300
 +
*Full-time students*: €225
  
==== Accommodation and Travel  ====
+
*Training fee is €990 for two days, see Training tab above
  
== Travel ==
+
<nowiki>*</nowiki> We need some kind of proof of your full-time student status. Either ask your local OWASP chapter leader to vouch for you by email to [email protected].org, or email Kate a scanned image of your student ID (please compress the file size&nbsp;:).  
Stockholm's foremost international airport is Arlanda (ARN). Clean and convenient speed trains will take you between Arlanda and Stockholm Central in 20 minutes. You can also fly to Stockholm Skavsta (NYO) or Stockholm Västerås (VST) where coaches take you to Stockholm Central in 1 h 20 min.
 
  
== Accommodation ==
+
==== Travel & Hotels  ====
  
You can choose hotel/hostel freely in Stockholm but we provide three suggestions with pre-booked rooms. Before you book '''check with sites like [http://www.hotels.com hotels.com] since they might have better prices for the very same hotels!'''
+
== Travel  ==
  
[[Image:Stockholm_map_with_hotels_and_public_transportation.jpg]]
+
Stockholm's foremost international airport is Arlanda (ARN). Clean and convenient speed trains will take you between Arlanda and Stockholm Central in 20 minutes. You can also fly to Stockholm Skavsta (NYO) or Stockholm Västerås (VST) where coaches take you to Stockholm Central in 1 h 20 min.  
  
Subways and buses are convenient and safe and will take you right up to the venue (station/stop "Universitetet") from these three hotels:
+
== Accommodation  ==
  
'''Best Western Time Hotel'''<br>
+
You can choose hotel/hostel freely in Stockholm but we provide three suggestions with pre-booked rooms. Before you book '''check with sites like [http://www.hotels.com hotels.com] since they might have better prices for the very same hotels!'''
Why? Closest to the university, direct bus or subway to the conference<br>
 
[http://www.timehotel.se/index.aspx?languageID=5 Best Western Time Hotel]<br>
 
Single room: 1395 SEK/€145/$195<br>
 
Double room: 1575 SEK/€160/$220<br>
 
Rooms pre-booked until May 6 under code "G#73641 OWASP"<br>
 
  
'''Scandic Continental'''<br>
+
[[Image:Stockholm map with hotels and public transportation.jpg]]  
Why? Right at the Central Station, convenient travel to and from airport, direct subway to the conference<br>
 
[http://www.scandichotels.com/en/Hotels/Countries/Sweden/Stockholm/Hotels/Scandic-Continental-Stockholm/ Scandic Continental]<br>
 
Single room: 1590 SEK/€165/$220<br>
 
Double room: 1690 SEK/€175/$235<br>
 
Rooms pre-booked until early May under code "OWASP"<br>
 
  
'''Fridhemsplan's Hostel'''<br>
+
Subways and buses are convenient and safe and will take you right up to the venue (station/stop "Universitetet") from these three hotels:
Why? Affordable stay in Stockholm's nicest hostel, direct bus to the conference<br>
+
 
[http://fridhemsplan.se/?p=Main&c= Fridhemsplan's Hostel]<br>
+
'''Best Western Time Hotel'''<br> Why? Closest to the university, direct bus or subway to the conference<br> [http://www.timehotel.se/index.aspx?languageID=5 Best Western Time Hotel]<br> Single room: 1395 SEK/€145/$195<br> Double room: 1575 SEK/€160/$220<br> Rooms pre-booked until May 6 under code "G#73641 OWASP"<br>
Rooms cost €35-€55 ($50-$80)<br>
+
 
Booking via John Wilander ([email protected]). First-come-first-served with priority to students or people who have the need ;).
+
'''Scandic Continental'''<br> Why? Right at the Central Station, convenient travel to and from airport, direct subway to the conference<br> [http://www.scandichotels.com/en/Hotels/Countries/Sweden/Stockholm/Hotels/Scandic-Continental-Stockholm/ Scandic Continental]<br> Single room: 1590 SEK/€165/$220<br> Double room: 1690 SEK/€175/$235<br> Rooms pre-booked until early May under code "OWASP"<br>
 +
 
 +
'''Fridhemsplan's Hostel'''<br> Why? Affordable stay in Stockholm's nicest hostel, direct bus to the conference<br> [http://fridhemsplan.se/?p=Main&c= Fridhemsplan's Hostel]<br> Rooms cost €35-€55 ($50-$80)<br> Booking via John Wilander ([email protected]). First-come-first-served with priority to students or people who have the need&nbsp;;).  
  
 
==== Venue  ====
 
==== Venue  ====
Line 248: Line 447:
 
There will be a challenge posted on the conference wiki page the 21st every month up until the event. The winner will get free entrance to the conference. Be sure to sign up for [https://lists.owasp.org/mailman/listinfo/appsec_eu_2010 the conference mailing list] to get a monthly reminder.  
 
There will be a challenge posted on the conference wiki page the 21st every month up until the event. The winner will get free entrance to the conference. Be sure to sign up for [https://lists.owasp.org/mailman/listinfo/appsec_eu_2010 the conference mailing list] to get a monthly reminder.  
  
== AppSec Research Challenge X: Build an Enterprise Java Rootkit ==
+
== AppSec Research Challenge X: Build an Enterprise Java Rootkit ==
  
The tenth challenge is here!
+
The tenth challenge is here!  
  
Jeff Williams, chairman of OWASP, gave a very interesting talk at last year's Black Hat US and OWASP AppSec US -- [http://www.blackhat.com/presentations/bh-usa-09/WILLIAMS/BHUSA09-Williams-EnterpriseJavaRootkits-PAPER.pdf "Enterprise Java Rootkits -- Hardly Anyone Watches the Developers"]. Now it's time for you to write a rootkit yourself, exploring Jeff's techniques and more.
+
Jeff Williams, chairman of OWASP, gave a very interesting talk at last year's Black Hat US and OWASP AppSec US -- [http://www.blackhat.com/presentations/bh-usa-09/WILLIAMS/BHUSA09-Williams-EnterpriseJavaRootkits-PAPER.pdf "Enterprise Java Rootkits -- Hardly Anyone Watches the Developers"]. Now it's time for you to write a rootkit yourself, exploring Jeff's techniques and more.  
  
'''The Project to Fool'''<br>
+
'''The Project to Fool'''<br> Your assignment is to be the evil developer who implements and hides a backdoor in a Java servlet. We've implemented a very simple login web application and exported the Eclipse project ([http://www.owasp.org/images/1/16/OWASP_AppSec_Research_2010_Challenge_X.zip zip here]). We will use this project to evaluate your submissions. It's a simple servlet/jsp project that we deployed on Tomcat 6.0. It even contains an evil output of user credentials to a temp file (not yet hidden though) to get you started. Screenshot from the app and the project structure:  
Your assignment is to be the evil developer who implements and hides a backdoor in a Java servlet. We've implemented a very simple login web application and exported the Eclipse project ([http://www.owasp.org/images/1/16/OWASP_AppSec_Research_2010_Challenge_X.zip zip here]). We will use this project to evaluate your submissions. It's a simple servlet/jsp project that we deployed on Tomcat 6.0. It even contains an evil output of user credentials to a temp file (not yet hidden though) to get you started. Screenshot from the app and the project structure:
 
  
 +
<br> [[Image:Appsec research 2010 challenge X eclipse project.jpg]] [[Image:Appsec research 2010 challenge X login screen.jpg]]
  
[[Image:Appsec research 2010 challenge X eclipse project.jpg]] [[Image:Appsec research 2010 challenge X login screen.jpg]]
+
'''Rules'''<br>
  
'''Rules'''<br>
+
*You must explain what your changes do (we need to evaluate your rootkit!)  
* You must explain what your changes do (we need to evaluate your rootkit!)
+
*The original features + look and feel must be preserved  
* The original features + look and feel must be preserved
+
*Your additions should preferably look like security features such as IP whitelisting, logging, anti-CSRF, frequency blocking etc.  
* Your additions should preferably look like security features such as IP whitelisting, logging, anti-CSRF, frequency blocking etc.
+
*You're only allowed to change the servlet (Login.java), and the gif image (appsec_research_challenge_X.gif)  
* You're only allowed to change the servlet (Login.java), and the gif image (appsec_research_challenge_X.gif)
+
*You do not have to use the jsps  
* You do not have to use the jsps
+
*The original size of Login.java is 1,856 bytes and it mustn't grow to more than 4,000 bytes  
* The original size of Login.java is 1,856 bytes and it mustn't grow to more than 4,000 bytes
+
*The gif image mustn't grow in size and should look close enough to the original to fool the committee  
* The gif image mustn't grow in size and should look close enough to the original to fool the committee
+
*Code should "look" readable, i e not minimized too heavily
* Code should "look" readable, i e not minimized too heavily
 
  
'''How To Win'''<br>
+
'''How To Win'''<br> The organization committee will evaluate who has been able to hide the most evil stuff while complying to the rules. The more malicious functionality and the more clever disguise -- the more "points". All submissions must be posted as links or pasted code in [http://sla.ckers.org/forum/read.php?11,33928 this sla.ckers.org thread]. Send an email to [email protected] when you post code or need attention. Deadline April 20.  
The organization committee will evaluate who has been able to hide the most evil stuff while complying to the rules. The more malicious functionality and the more clever disguise -- the more "points". All submissions must be posted as links or pasted code in [http://sla.ckers.org/forum/read.php?11,33928 this sla.ckers.org thread]. Send an email to [email protected] when you post code or need attention. Deadline April 20.
 
  
 +
<br>
  
==== CFP, CFT, old challenges ====
+
==== Archive  ====
  
== Call for Papers and Proposals (closed) ==
+
== Call for Papers and Proposals (closed) ==
  
 
[[Image:AppSec Research 2010 2nd cfp.png]]  
 
[[Image:AppSec Research 2010 2nd cfp.png]]  
Line 292: Line 490:
 
=== Submission Deadline and Instructions  ===
 
=== Submission Deadline and Instructions  ===
  
'''Update''': Submission deadline for full-papers ("Publish or Perish") has been '''extended to March 7th 23:59''' (Apia, Samoa time) due to numerous requests. Submit your paper to [https://www.easychair.org/login.cgi?a=c01e98d04e4e;iid=20045 AppSec Research 2010 (EasyChair)].
+
'''Update''': Submission deadline for full-papers ("Publish or Perish") has been '''extended to March 7th 23:59''' (Apia, Samoa time) due to numerous requests. Submit your paper to [https://www.easychair.org/login.cgi?a=c01e98d04e4e;iid=20045 AppSec Research 2010 (EasyChair)].  
  
 
Full-paper submissions should be at most 12 pages long and must be in the Springer LNCS style for "Proceedings and Other Multiauthor Volumes". Templates for preparing papers in this style for LaTeX, Word, etc can be downloaded from: http://www.springer.com/computer/lncs?SGWID=0-164-7-72376-0. Full papers must be submitted in a form suitable for anonymous review: '''remove author names and affiliations from the title page, and avoid explicit self-referencing in the text'''.  
 
Full-paper submissions should be at most 12 pages long and must be in the Springer LNCS style for "Proceedings and Other Multiauthor Volumes". Templates for preparing papers in this style for LaTeX, Word, etc can be downloaded from: http://www.springer.com/computer/lncs?SGWID=0-164-7-72376-0. Full papers must be submitted in a form suitable for anonymous review: '''remove author names and affiliations from the title page, and avoid explicit self-referencing in the text'''.  
  
Submission for "Demo or Die" and "Present or Repent" closed on February 7th.
+
Submission for "Demo or Die" and "Present or Repent" closed on February 7th.  
  
Decision notification: April 7th
+
Decision notification: April 7th  
  
 
=== Program Committee (for review of full-papers)  ===
 
=== Program Committee (for review of full-papers)  ===
Line 305: Line 503:
  
 
== Call for Training (closed)  ==
 
== Call for Training (closed)  ==
(Info kept here for reference)<br>
+
 
OWASP is currently soliciting training proposals for the OWASP AppSec Research 2010 Conference which will take place at Stockholm University in Sweden, on June 21st through June 24th 2010. There will be training courses on June 21st and 22nd followed by plenary sessions on the 23rd and 24th with three tracks per day.  
+
(Info kept here for reference)<br> OWASP is currently soliciting training proposals for the OWASP AppSec Research 2010 Conference which will take place at Stockholm University in Sweden, on June 21st through June 24th 2010. There will be training courses on June 21st and 22nd followed by plenary sessions on the 23rd and 24th with three tracks per day.  
  
 
We are seeking training proposals on the following topics (in no particular order):  
 
We are seeking training proposals on the following topics (in no particular order):  
Line 331: Line 529:
 
As part of the [http://www.owasp.org/index.php/Category:OWASP_Education_Project OWASP Education Project], OWASP is starting an official list of trainers on the OWASP web site. This list (mentioning the trainer - course and contact details) will cover all trainers that performed training at OWASP conferences, together with their aggregated scores on the course feedback forms. Of course, this is opt-in. Please let us know if you are interested to participate in this program (tick the check-box on the application form).  
 
As part of the [http://www.owasp.org/index.php/Category:OWASP_Education_Project OWASP Education Project], OWASP is starting an official list of trainers on the OWASP web site. This list (mentioning the trainer - course and contact details) will cover all trainers that performed training at OWASP conferences, together with their aggregated scores on the course feedback forms. Of course, this is opt-in. Please let us know if you are interested to participate in this program (tick the check-box on the application form).  
  
== AppSec Research Challenge 9: Crack 'Em Hashes (closed) ==
+
== AppSec Research Challenge 9: Crack 'Em Hashes (closed) ==
 +
 
 +
February's AppSec Research 2010 challenge is about breaking hashed passwords. It starts off easy with the old LM hash and ends with SHA256 and GOST3411.
  
February's AppSec Research 2010 challenge is about breaking hashed passwords. It starts off easy with the old LM hash and ends with SHA256 and GOST3411.
+
[[Image:Owasp appsec research 2010 hash challenge.jpg]]
  
[[Image:Owasp_appsec_research_2010_hash_challenge.jpg]]
+
'''How To Win'''<br> The first one to publish each broken password gets points according to the table below but at the same time helps the others since the password is the salt of the next hash. So you have to decide -- should you publish your cracked password and collect your points before the others or should you keep it a secret to get a head start cracking the next one? Deadline it March 21st.  
  
'''How To Win'''<br>
+
To collect points for a password you must be the first one to publish that broken password on [http://sla.ckers.org/forum/read.php?11,33533 this sla.ckers.org thread]. Please send an email to [email protected] at the same time so we can correct any misunderstandings. For instance we can happen to run into hash collisions, where someone finds another mixed alpha password of max 5 characters that concatenated with the right salt produces the same hash. In such a case we will publish the real password and give points to the one who found the collision.  
The first one to publish each broken password gets points according to the table below but at the same time helps the others since the password is the salt of the next hash. So you have to decide -- should you publish your cracked password and collect your points before the others or should you keep it a secret to get a head start cracking the next one? Deadline it March 21st.
 
  
To collect points for a password you must be the first one to publish that broken password on [http://sla.ckers.org/forum/read.php?11,33533 this sla.ckers.org thread]. Please send an email to [email protected] at the same time so we can correct any misunderstandings. For instance we can happen to run into hash collisions, where someone finds another mixed alpha password of max 5 characters that concatenated with the right salt produces the same hash. In such a case we will publish the real password and give points to the one who found the collision.
+
The one with the most points on March 21st wins a free ticket to the conference!
  
The one with the most points on March 21st wins a free ticket to the conference!
+
'''Points to Earn'''<br>
  
'''Points to Earn'''<br>
+
*pwd1 (LM) =&gt; 1 point  
* pwd1 (LM) => 1 point
+
*pwd2 (MD2) =&gt; 3 points  
* pwd2 (MD2) => 3 points
+
*pwd3 (MD4) =&gt; 5 points  
* pwd3 (MD4) => 5 points
+
*pwd4 (MD5) =&gt; 9 points  
* pwd4 (MD5) => 9 points
+
*pwd5 (RIPEMD160) =&gt; 15 points  
* pwd5 (RIPEMD160) => 15 points
+
*pwd6 (SHA1) =&gt; 25 points  
* pwd6 (SHA1) => 25 points
+
*pwd7 (SHA256) =&gt; 50 points  
* pwd7 (SHA256) => 50 points
+
*pwd8 (GOST3411) =&gt; 100 points
* pwd8 (GOST3411) => 100 points
 
  
'''The Hashes'''<br>
+
'''The Hashes'''<br> Each password comprises of a-zA-Z (mixed alpha) and is max 5 characters long. With salt that means max 10 mixed alpha characters as input to the hash function. All hashes here are in hex format. The Java source code has all the details. The plus operator means string concatenation.  
Each password comprises of a-zA-Z (mixed alpha) and is max 5 characters long. With salt that means max 10 mixed alpha characters as input to the hash function. All hashes here are in hex format. The Java source code has all the details. The plus operator means string concatenation.
 
  
* LM(pwd1)       0C04DACA901299DBAAD3B435B51404EE
+
*LM(pwd1) 0C04DACA901299DBAAD3B435B51404EE  
* MD2(pwd2 + pwd1)       16189F5462BF906E9D88CF6F152DE86F
+
*MD2(pwd2 + pwd1) 16189F5462BF906E9D88CF6F152DE86F  
* MD4(pwd3 + pwd2)       FA8F46A6D347087D6980C3FA77DD4DE9
+
*MD4(pwd3 + pwd2) FA8F46A6D347087D6980C3FA77DD4DE9  
* MD5(pwd4 + pwd3)       425B33D6F60394C897B8413B5C185845
+
*MD5(pwd4 + pwd3) 425B33D6F60394C897B8413B5C185845  
* RIPEMD160(pwd5 + pwd4) 35F34671D30472D403937820DCABC1C78C837071
+
*RIPEMD160(pwd5 + pwd4) 35F34671D30472D403937820DCABC1C78C837071  
* SHA1(pwd6 + pwd5)       AE81A30510B2931921934218636B26A803330EB1
+
*SHA1(pwd6 + pwd5) AE81A30510B2931921934218636B26A803330EB1  
* SHA256(pwd7 + pwd6)     B2FF0269E927C6559804A37590A0688C45DF143F85CEE0E3F239F846B65C9644
+
*SHA256(pwd7 + pwd6) B2FF0269E927C6559804A37590A0688C45DF143F85CEE0E3F239F846B65C9644  
* GOST3411(pwd8 + pwd7)   16CC9F1FF65688E040F5ADA82A41A258FF948769CDA4C4A17D85228A6F358971
+
*GOST3411(pwd8 + pwd7) 16CC9F1FF65688E040F5ADA82A41A258FF948769CDA4C4A17D85228A6F358971
  
Example: Given that pwd1 is "Win" and pwd2 is "You", the hash 16189F5462BF906E9D88CF6F152DE86F is the result of MD2("YouWin"). Now pwd2 will be the salt when you crack pwd3.
+
Example: Given that pwd1 is "Win" and pwd2 is "You", the hash 16189F5462BF906E9D88CF6F152DE86F is the result of MD2("YouWin"). Now pwd2 will be the salt when you crack pwd3.  
  
'''The Source Code'''<br>
+
'''The Source Code'''<br> The source code we've used to produce the hashes is available here [http://www.owasp.org/images/7/79/OwapsAppSecResearch2010HashChallenge.zip zip]. It's Java and all but the LM hash is done with [http://www.bouncycastle.org/latest_releases.html Bouncy Castle 1.4.5].  
The source code we've used to produce the hashes is available here [http://www.owasp.org/images/7/79/OwapsAppSecResearch2010HashChallenge.zip zip]. It's Java and all but the LM hash is done with [http://www.bouncycastle.org/latest_releases.html Bouncy Castle 1.4.5].
 
  
 +
<br>
  
 
== AppSec Research Challenge 8: Construct an OWASP Polyglot (closed)  ==
 
== AppSec Research Challenge 8: Construct an OWASP Polyglot (closed)  ==
Line 382: Line 579:
 
'''Rules'''  
 
'''Rules'''  
  
*Make your polyglot out of the regular OWASP logo in the upper left corner of this wiki (circle with the wasp).
+
*Make your polyglot out of the regular OWASP logo in the upper left corner of this wiki (circle with the wasp).  
 
*The file size must not grow.  
 
*The file size must not grow.  
 
*Pixel colors in the gif must not differ more than 5 in red, green, or blue. Ex: If a pixel originally had rgb 100,100,100 then 104,95,96 is OK.  
 
*Pixel colors in the gif must not differ more than 5 in red, green, or blue. Ex: If a pixel originally had rgb 100,100,100 then 104,95,96 is OK.  
Line 393: Line 590:
 
#A quine. The polyglot outputs its own source code on the HTML page.
 
#A quine. The polyglot outputs its own source code on the HTML page.
  
'''How to get started'''
+
'''How to get started'''  
  
 
Jasvir Nagra gave a talk on these kind of polyglots and published a gif/JavaScript polyglot on [http://www.thinkfu.com/blog/gifjavascript-polyglots his blog]. A good starting point is his gif file.&nbsp;Jasvir has also written an extensive article on gif/perl polyglots which explains how to get code into the gif file. Check out [http://search.cpan.org/~jnagra/Perl-Visualize-1.02/Visualize.pm#HOW_IT_ALL_WORKS his guide].  
 
Jasvir Nagra gave a talk on these kind of polyglots and published a gif/JavaScript polyglot on [http://www.thinkfu.com/blog/gifjavascript-polyglots his blog]. A good starting point is his gif file.&nbsp;Jasvir has also written an extensive article on gif/perl polyglots which explains how to get code into the gif file. Check out [http://search.cpan.org/~jnagra/Perl-Visualize-1.02/Visualize.pm#HOW_IT_ALL_WORKS his guide].  
Line 399: Line 596:
 
'''How to win'''  
 
'''How to win'''  
  
Submit your entries in [http://sla.ckers.org/forum/read.php?11,33121 this sla.ckers.org thread]. Either the first complete polyglot or the most complete polyglot wins. We will most probably provide you with a gif checker that validates the color differences. Check the thread.&nbsp;
+
Submit your entries in [http://sla.ckers.org/forum/read.php?11,33121 this sla.ckers.org thread]. Either the first complete polyglot or the most complete polyglot wins. We will most probably provide you with a gif checker that validates the color differences. Check the thread.&nbsp;  
  
 
== AppSec Research Challenge 7: X-Mas Capture the Flag (closed)  ==
 
== AppSec Research Challenge 7: X-Mas Capture the Flag (closed)  ==
Line 423: Line 620:
 
<br>  
 
<br>  
  
== AppSec Research Challenge 6: Design the Conference Logo (closed) ==
+
== AppSec Research Challenge 6: Design the Conference Logo (closed) ==
  
'''Note''': This challenge is re-opened. Submit by February 21st.
+
'''Note''': This challenge is re-opened. Submit by February 21st.  
  
 
November's AppSec Research 2010 Challenge asks you to design the conference logotype. So far we have used this:  
 
November's AppSec Research 2010 Challenge asks you to design the conference logotype. So far we have used this:  
Line 551: Line 748:
 
'''Submissions were made as comments to the [http://owaspsweden.blogspot.com/2009/08/appsec-research-2010-challenge-3.html challenge 3 blogpost on Owasp Sweden].''' Check it out.  
 
'''Submissions were made as comments to the [http://owaspsweden.blogspot.com/2009/08/appsec-research-2010-challenge-3.html challenge 3 blogpost on Owasp Sweden].''' Check it out.  
  
== AppSec Research Challenge 2: OWASP Crossword Puzzle (closed) ==
+
== AppSec Research Challenge 2: OWASP Crossword Puzzle (closed) ==
  
 
July's crossword challenge is over. Many permutations arrived in our inbox but it was tricky to get it completely right. Congratulations to Johannes Dahse and Johan Nilsson who in the end were allowed to join forces to be able to find the correct solution. They win a 50&nbsp;% conference ticket discount each.  
 
July's crossword challenge is over. Many permutations arrived in our inbox but it was tricky to get it completely right. Congratulations to Johannes Dahse and Johan Nilsson who in the end were allowed to join forces to be able to find the correct solution. They win a 50&nbsp;% conference ticket discount each.  
Line 559: Line 756:
 
[[Image:Appsec research 2010 challenge 2 solution.gif]]  
 
[[Image:Appsec research 2010 challenge 2 solution.gif]]  
  
== AppSec Research Challenge 1: Input Validation and Regular Expressions (closed) ==
+
== AppSec Research Challenge 1: Input Validation and Regular Expressions (closed) ==
  
 
'''This challenge is over'''. The winner was Partik Nordlén. To see the solution(s), please visit the [https://lists.owasp.org/pipermail/appsec_eu_2010/2009-July/000000.html appsec_eu_2010 mailing list archive].  
 
'''This challenge is over'''. The winner was Partik Nordlén. To see the solution(s), please visit the [https://lists.owasp.org/pipermail/appsec_eu_2010/2009-July/000000.html appsec_eu_2010 mailing list archive].  
Line 581: Line 778:
 
'''Email your solution to Martin Holst Swende &lt;[email protected]&gt;'''. The first correct answer wins a free ticket to the conference. The free ticket is personal and the judgement of the organizing committee can not be overruled&nbsp;:).  
 
'''Email your solution to Martin Holst Swende &lt;[email protected]&gt;'''. The first correct answer wins a free ticket to the conference. The free ticket is personal and the judgement of the organizing committee can not be overruled&nbsp;:).  
  
 
+
<br> <headertabs />
<headertabs />
 

Revision as of 21:38, 6 April 2010


Welcome

Invitation

Ladies and Gentlemen,

In June 21-24, 2010 let's all meet in beautiful Stockholm, Sweden. The OWASP chapters in Sweden, Norway, and Denmark hereby invite you to OWASP AppSec Research 2010.

If you have any questions, please email the conference chair: john.wilander at owasp.org

Stockholm old town small.jpg

Sponsors

Diamond sponsor:
AppSec Research 2010 Microsoft diamond sponsor.jpg

Gold sponsors:
Cybercom logo.png Portwise logo.png
Fortify logo AppSec Research 2010.png Omegapoint logo.png

Silver sponsors (3 taken, 5 open):
Mnemonic logo.png AppSec Research 2010 sponsor Nixu logo.jpg AppSec Research 2010 Google 20k sponsor.jpg

Lunch sponsors (1 taken, 1 open):
IIS logo.png

Coffee break sponsors (1 taken, 3 open):
MyNethouse logo.png

Media sponsors:
AppSec Research 2010 Help Net Security sponsor.jpg

For full sponsoring program see the Sponsoring tab above.

"AppSec Research".equals("AppSec Europe")

This conference was formerly known as OWASP AppSec Europe. We have added 'Research' to highlight that we invite both industry and academia. All the regular AppSec Europe visitors and topics are welcome along with contributions from universities and research institutes.

This will be the European conference for anyone interested in or working with application security. Co-host is the Department of Computer and Systems Science at Stockholm University, offering a great venue in the fabulous Aula Magna.

Countdown Challenges -- Free Tickets to Win!

There will be a challenge posted on the conference wiki page the 21st every month up until the event. The winner will get free entrance to the conference. What are you waiting for? Go to the Challenges tab and have fun!

Organizing Committee

• John Wilander, chapter leader Sweden (chair)
• Mattias Bergling (vice chair)
• Alan Davidson, Stockholm University/Royal Institute of Technology (co-host)
• Ulf Munkedal, chapter leader Denmark
• Kåre Presttun, chapter leader Norway
• Stefan Pettersson (sponsoring coordinator)
• Carl-Johan Bostorp (schedule and event coordinator)
• Martin Holst Swende (coffee/lunch/dinner)
• Predrag Mitrovic, OWASP Sweden Board
• Kate Hartmann, OWASP
• Sebastien Deleersnyder, OWASP Board

Welcome to Stockholm this year!
Regards, John Wilander

June 21-22 (Training)

Training Registration is now OPEN

Application security training is given the first two days, June 21-22. The price is €990 (~$1.350) for a two-day course. Take the chance to learn from the best!

Course 1: Threat Modeling and Architecture Review (two days)

AppSec Research 2010 Pravir Chandra.jpg

Pravir Chandra, Fortify Software

Abstract: Threat Modeling and Architecture Review are the cornerstones of a preventative approach to Application Security. By combining these topics into single comprehensive course attendees can get a complete understanding of how to understand the threat an application faces and how the application will handle those potential threats. This enables the risk to be accurately assessed and appropriate changes or mitigating controls recommended.

Trainer Bio: Pravir Chandra is Director of Strategic Services at Fortify where he works with clients to build and optimize software security assurance programs. Pravir is widely recognized in the industry for his expertise in software security and code analysis, and also for his ability to apply technical knowledge strategically from a business perspective. His book, Network Security with OpenSSL is a popular reference on protecting software applications through cryptography and secure communications. His varied special project experience includes creating and leading the Open Software Assurance Maturity Model (OpenSAMM) project

--> Register here

Course 2: Introduction to Malware Analysis (two days)

AppSec Research 2010 Jason Geffner.jpg

Jason Geffner, Next Generation Security Software (NGS), and Scott Lambert, Microsoft

Abstract: Security researchers are facing a growing problem in the complexity of malicious executables. While dynamic black-box automation tools exist to discover what malware will do on a given execution, it is often important for an analyst to know the full capabilities of a given malware sample. What port does it listen on? What password does it expect for backdoor access? What files will it write to? What will it do tomorrow that it didn't do today? This class will focus on teaching attendees the steps required to understand the functionality of given malware samples. This is a hands-on course. Attendees will work on real-world malware through a series of lab exercises designed to build their expertise in understanding the analysis process.

Learning Objectives:

  • An understanding of how to use reverse engineering tools
  • An understanding of low-level code and data flow
  • PE File format
  • x86 Assembly language
  • API functions often used by malware
  • Anti-analysis tricks and how to defeat them
  • Exploits and Shellcode
  • A methodology for analyzing malware with and without the use of specialized tools

Trainer Bio: Jason Geffner joined Next Generation Security Software Ltd. in June of 2007 as a Principal Security Consultant. Jason focuses on performing security reviews of source code and designs, reverse engineering software protection methods and DRM protection methods, deobfuscating and analyzing malware, penetration testing web applications and network infrastructures, and developing automated security analysis tools.

--> Register here

Course 3: Building Secure Ajax and Web 2.0 Applications (two days)

AppSec Research 2010 Dave Wichers.jpg

Dave Wichers, Aspect Security

Abstract: Students gain hands-on testing experience with freely available web application security test tools to find and diagnose flaws and learn how to identify them in their own projects. Because finding flaws is worthless without effective communication, the course also covers the process of creating and communicating software security flaws effectively. In addition, Aspect’s engineers are leaders in the AppSec Community and will offer the students an amazing perspective.

From the course outline:
CSS Attacks, Browser Add On Attacks, RSS / Data Feed Attacks, Microsoft Active X, Adobe Flash/Flex/AIR, Silverlight, Java FX, Ajax Mashups, Same Origin Policy, JavaScript, Web 2.0 CSRF Attacks, XHR JSON Forgery, Best Practice: Check HTTP Headers, Best Practice: Unique ID For XHR, JSON and XML Based XSS, How to use OWASP AntiSamy, Blended Threats, Dealing with Ajax Toolkits, Best Practice: Fuzzing ...

Trainer Bio: Dave Wichers is a member of the OWASP Board and a coauthor, along with Jeff Williams, of all previous versions of the OWASP Top Ten. Dave is also the Chief Operating Officer of Aspect Security, a company that specializes in application security services. Mr. Wichers brings over twenty years of experience in the information security field. Prior to cofounding Aspect, he ran the Application Security Services Group at a large data center company, Exodus Communications. His current work involves helping customers, from small e-commerce sites to Fortune 500 corporations and the U.S. Government, secure their applications by providing application security design, architecture, and SDLC support services: including code review, application penetration testing, security policy development, security consulting services, and developer training.

--> Register here

Course 4: Assessing and Exploiting Web Apps with Samurai-WTF (two days)

AppSec Research 2010 Justin Searle.jpg

Justin Searle, InGuardians

Abstract: This course will focus on using open source tools to perform web application assessments. The course will take attendees through the process of application assessment using the open source tools included in the Samurai Web Testing Framework Live CD (Samurai-WTF). Day one will take students through the steps and open source tools used to assess applications for vulnerabilities. Day two will focus on the exploitation of web app vulnerabilities, spending half the day on server side attacks and the other half of the day on client side attacks. The latest tools and techniques will be use throughout the course, including several tools developed by the trainers themselves.

Trainer Bio: Justin Searle, a Senior Security Analyst with InGuardians, specializes in web application, network, and embedded penetration testing. Justin has presented at top security conferences including DEFCON, ToorCon, ShmooCon, and SANS. Justin has an MBA in International Technology and is CISSP and SANS GIAC-certified in incident handling and hacker techniques (GCIH) and intrusion analysis (GCIA). Justin is one of the founders and lead developers of Samurai-WTF.

--> Register here

Course 5: Securing Web Services (two days)

AppSec Research 2010 Jason Li.jpg

Jason Li, Aspect Security

Abstract: Aspect Security offers a one or two day course titled Securing Web Services designed to focus on the most important messages regarding the development and of secure web services. The objective for this course is to ensure that developers understand the real risks associated with Service Oriented Architectures, what standard are available to help, and how to use the standards. The course includes a combination of lecture and demonstration designed to provide detailed guidance regarding the implementation of specific security principles and functions.

Trainer Bio: Jason Li is a Senior Application Security Engineer for Aspect Security where he performs application security assessments and architecture reviews, as well as application security training, to a wide variety of financial and government customers. Jason is an active OWASP leader, contributing to several OWASP projects and serving on the OWASP Global Projects Committee. He holds a Post-Masters certificate in Computer Science and concentration in Information Security from Johns Hopkins University and a Masters degree in Computer Science from Cornell University.

--> Register here

June 23

Conference Day 1 - June 23, 2010

Track 1 Track 2 Track 3
08:00-08:50 Registration and Coffee
08:50-09:00 Welcome to OWASP AppSec Research 2010 Conference

John Wilander, OWASP Sweden & Dave Wichers, OWASP Foundation

09:00-10:00 Cross-Domain Theft and the Future of Browser Security

Chris Evans, Information Security Engineer, and Ian Fette, Product Manager for Chrome Security, Google

10:10-10:45 BitFlip: Determine a Data's Signature Coverage from within the Application

Henrich Christopher Poehls

CsFire: Browser Enforced Mitigation Against CSRF

Lieven Desmet and Philippe De Ryck

Deconstructing ColdFusion

Chris Eng

10:45-11:10 Break - Expo CTF Kick-Off


11:10-11:45 Towards Building Secure Web Mashups

Wouter Joosen

Automated vs. Manual Security: You Can't Filter The Stupid

David Byrne and Charles Henderson

How to Render SSL Useless

Ivan Ristic

11:55-12:30

Enterprise security patterns for RESTful Web Services

Francois Lascelles

Web Frameworks and How They Kill Traditional Security Scanning

Christian Hang

The State of SSL in the World

Michael Boman

12:30-13:45 Lunch - Expo - CTF
13:45-14:20 Securing Web Applications with ESAPI

Ken Sipe

Beyond the Same Origin Policy

Jasvir Nagra and Mike Samuel

SymFileFuzzer - a New File Fuzzer Tool

Komal Randive

14:30-15:05 Security Toolbox for .NET Development and Testing

Johan Lindfors and Dag König

Cross-Site Location Jacking (XSLJ) (not really)

David Lindsay and Eduardo Vela Nava

Owning Oracle: Sessions and Credentials

Wendel G. Henrique and Steve Ocepek

15:05-15:30 Break - Expo - CTF
15:30-16:05 Value Objects a la Doman-Driven Security: A Design Mindset to Avoid SQL Injection and Cross-Site Scripting Vulnerabilities

Dan Bergh Johnsson

New Insights into Clickjacking

Marco Balduzzi

Session Fixation - the Forgotten Vulnerability?

Michael Schrank, Bastian Braun and Martin Johns

16:15-17:00 Panel Discussion: To Be Announced

June 24

Conference Day 2 - June 23, 2010
Track 1 Track 2 Track 3
09:00-10:00 The Security Development Lifecycle -- The Creation and Evolution of a Security Development Process
Steve Lipner, Senior Director of Security Engineering Strategy, Microsoft Corporation
10:10-10:45

Building Security In Maturity Model: A Review of Successful Software Security Programs in Europe

Gabriele Giuseppini and Terri Randolph

Promon TestSuite -- Client Based Penetration Testing Tool

Folker den Braber and Tom Lysemose Hansen

A Taint Mode for Python via a Library
2.0

Juan José Conti and Alejandro Russo

10:45-11:10 Break - Expo - CTF
11:10-11:45

Microsoft's Security Development Lifecycle for Agile Development

Nick Coblentz

Detecting and Protecting You Users from 100% of all Malware -- How?

Bradley Anstis and Ellynora Nicoll

OPA: Language Support for a Sane, Safe and Secure Web

David Rajchenbach-Teller and François-Régis Sinot

11:55-12:30

Secure Application Development for the Enterprise: Practical, Real-World Tips

Michael Craigue

Responsibility for the Harm and Risk of Software Security Flaws

Cassio Goldschmidt

Secure the Clones: Static Enforcement of Policies for Secure Object Copying

Thomas Jensen and David Pichardie

12:30-13:45 Lunch - Expo - CTF
13:45-14:20

Product Security Management in Agile Product Management

Antti Vähä-Sipilä

Hacking by Numbers

Tom Brennan

Safe Wrappers and Sane Policies for Self Protecting JavaScript

Jonas Magazinius, Phu H. Phung and David Sands

14:30-15:05

OWASP Top 10 2010

Dave Wichers

Application Security Scoreboard in the Sky

Chris Eng

On the Privacy of File Sharing Services

Nick Nikiforakis, Francesco Gadaleta, Yves Younan, and Wouter Joosen

15:05-15:30 Break - Expo - CTF
15:30-16:00 CTF Price Ceremony, Announcement of OWASP AppSec EU 2011, Closing Notes

Invited Talks

"Cross-Domain Theft and the Future of Browser Security"

Appsec research 2010 invited talk 1.jpg

Chris Evans
Troublemaker, Information Security Engineer, and Tech Lead at Google inc.
Also the sole author of vsftpd.

Ian Fette
Product Manager for Chrome Security and Google's Anti-Malware initiative

Abstract
The web browser, and associated machinery, is on the front line of attacks. We will first look at design-level problems with the traditional browser in terms of monolithic architecture and fundamental problems with the same-origin policy. We will then look at the types of solution that are starting to appear in browsers such as Google Chrome and Internet Explorer. We will look at other important browser-based defenses such as Safe Browsing. We will detail what a future browser might look like that has a much more secure design, but is still usable on the wide variety of web sites that people use daily.

"The Security Development Lifecycle -- The Creation and Evolution of a Security Development Process"

Appsec research 2010 invited talk 2.jpg

Steve Lipner
Senior Director of Security Engineering Strategy, Trustworthy Computing Security, Microsoft Corporation.
Co-author of "The Security Development Lifecycle", Microsoft Press (book cover above).

Abstract
This keynote will review the evolution of the Security Development Lifecycle (SDL) from its origins in the Microsoft “security pushes” of 2002-3 through its current status and application in 2010. It will emphasize the aspects of change and change management as the SDL and its user community have matured and grown and will conclude with a summary of some recent changes and additions to the SDL. Specific topics to be addressed include:

  • Motivations for introducing both the SDL and its predecessor processes.
  • Considerations in selling the process to management and sustaining a mandate over a prolonged period.
  • Scaling the SDL to an organization with tens of thousands of engineers.
  • Managing change.
  • The role of automation in the SDL.
  • Adaptation of the SDL to agile development processes.
  • Thoughts for organizations that are considering implementing the SDL.

The presentation will cover technical aspects of the SDL including a brief review of requirements and tools, and results.

Speaker Bio
Steven B. Lipner is senior director of Security Engineering Strategy at Microsoft Corp where he is responsible for programs that provide improved product security for Microsoft customers. Lipner leads Microsoft’s Security Development Lifecycle (SDL) team and is responsible for the definition of Microsoft’s SDL and for programs to make the SDL available to organizations beyond Microsoft. Lipner is also responsible for Microsoft’s corporate strategies related to government security evaluation of Microsoft products. Lipner joined Microsoft in 1999 and was initially responsible for the Microsoft Security Response Center. In the aftermath of the major computer “worm” incidents of 2001, Lipner and his team formulated and led programs that helped customers respond to the immediate challenges posed by software vulnerabilities and Internet worms. Lipner and his team also devised the strategy of “security pushes” that, as part of the Trustworthy Computing initiative, enabled Microsoft to make rapid improvements in the security of its software products and to change the corporate development culture to emphasize product security. The SDL is the product of these improvements, and is widely viewed as the industry’s leading secure software development process.

Before joining Microsoft, Lipner worked for a variety of software vendors and government contractors as a researcher, consultant, development manager and general manager in IT security. Many of the concepts whose development he led form the basis for today’s approaches to building secure systems. Some examples of these contributions include the application of virtual machine monitors (VMMs) as an approach to isolating security domains, and mathematical models for multilevel security.

Lipner is coauthor with Michael Howard of The Security Development Lifecycle (Microsoft Press, 2006) and is named as inventor on twelve U.S. patents and two pending applications in the field of computer and network security. He has authored numerous professional papers and conference presentations, and served on several National Research Council committees. He served two terms – a total of more than ten years – on the United States Information Security and Privacy Advisory Board and its predecessor. Lipner holds S.B. and S.M. degrees in Civil Engineering from the Massachusetts Institute of Technology and attended the Harvard Business School’s Program for Management Development.

Registration

Registration is now OPEN

Click Here To Register

Note: To save on processing expenses, all fees paid for the OWASP conference are non-refundable. OWASP can accommodate transfers of registrations from one person to another, if such an adjustment becomes necessary.

Stay Informed ... and Tell Others

Subscribe to the conference mailing list. This is the official information channel and you'll be the first to know about the program, invited speakers, opening of registration for training etc.

Add the event to your LinkedIn profle to tell all your business contacts that AppSec Research 2010 is the place to be.

Then get on the Twitter stream by using the tags #OWASP and #AppSecEU.

Conference Fees

  • Early Bird registration, February 7 - April 7: €300
  • Regular registration, April 8 and onwards: €350
  • OWASP individual members (not just chapter member): €300
  • Full-time students*: €225
  • Training fee is €990 for two days, see Training tab above

* We need some kind of proof of your full-time student status. Either ask your local OWASP chapter leader to vouch for you by email to [email protected], or email Kate a scanned image of your student ID (please compress the file size :).

Travel & Hotels

Travel

Stockholm's foremost international airport is Arlanda (ARN). Clean and convenient speed trains will take you between Arlanda and Stockholm Central in 20 minutes. You can also fly to Stockholm Skavsta (NYO) or Stockholm Västerås (VST) where coaches take you to Stockholm Central in 1 h 20 min.

Accommodation

You can choose hotel/hostel freely in Stockholm but we provide three suggestions with pre-booked rooms. Before you book check with sites like hotels.com since they might have better prices for the very same hotels!

Stockholm map with hotels and public transportation.jpg

Subways and buses are convenient and safe and will take you right up to the venue (station/stop "Universitetet") from these three hotels:

Best Western Time Hotel
Why? Closest to the university, direct bus or subway to the conference
Best Western Time Hotel
Single room: 1395 SEK/€145/$195
Double room: 1575 SEK/€160/$220
Rooms pre-booked until May 6 under code "G#73641 OWASP"

Scandic Continental
Why? Right at the Central Station, convenient travel to and from airport, direct subway to the conference
Scandic Continental
Single room: 1590 SEK/€165/$220
Double room: 1690 SEK/€175/$235
Rooms pre-booked until early May under code "OWASP"

Fridhemsplan's Hostel
Why? Affordable stay in Stockholm's nicest hostel, direct bus to the conference
Fridhemsplan's Hostel
Rooms cost €35-€55 ($50-$80)
Booking via John Wilander ([email protected]). First-come-first-served with priority to students or people who have the need ;).

Venue

AppSec Research 2010 Aula Magna.jpg

Sponsoring

We are now welcoming sponsors for OWASP AppSec Research 2010. Take the opportunity to support next year's major appsec event in Europe! The full sponsoring program is available as pdfs:

Sponsoring program in English: File:OWASP Sponsorship AppSec Research 2010 (eng).pdf

Sponsoring program in Swedish: File:OWASP Sponsorship AppSec Research 2010 (swe).pdf

Part of the sponsoring program
Part of the sponsoring program

Challenges

Countdown Challenges -- Free Tickets to Win!

There will be a challenge posted on the conference wiki page the 21st every month up until the event. The winner will get free entrance to the conference. Be sure to sign up for the conference mailing list to get a monthly reminder.

AppSec Research Challenge X: Build an Enterprise Java Rootkit

The tenth challenge is here!

Jeff Williams, chairman of OWASP, gave a very interesting talk at last year's Black Hat US and OWASP AppSec US -- "Enterprise Java Rootkits -- Hardly Anyone Watches the Developers". Now it's time for you to write a rootkit yourself, exploring Jeff's techniques and more.

The Project to Fool
Your assignment is to be the evil developer who implements and hides a backdoor in a Java servlet. We've implemented a very simple login web application and exported the Eclipse project (zip here). We will use this project to evaluate your submissions. It's a simple servlet/jsp project that we deployed on Tomcat 6.0. It even contains an evil output of user credentials to a temp file (not yet hidden though) to get you started. Screenshot from the app and the project structure:


Appsec research 2010 challenge X eclipse project.jpg Appsec research 2010 challenge X login screen.jpg

Rules

  • You must explain what your changes do (we need to evaluate your rootkit!)
  • The original features + look and feel must be preserved
  • Your additions should preferably look like security features such as IP whitelisting, logging, anti-CSRF, frequency blocking etc.
  • You're only allowed to change the servlet (Login.java), and the gif image (appsec_research_challenge_X.gif)
  • You do not have to use the jsps
  • The original size of Login.java is 1,856 bytes and it mustn't grow to more than 4,000 bytes
  • The gif image mustn't grow in size and should look close enough to the original to fool the committee
  • Code should "look" readable, i e not minimized too heavily

How To Win
The organization committee will evaluate who has been able to hide the most evil stuff while complying to the rules. The more malicious functionality and the more clever disguise -- the more "points". All submissions must be posted as links or pasted code in this sla.ckers.org thread. Send an email to [email protected] when you post code or need attention. Deadline April 20.


Archive

Call for Papers and Proposals (closed)

AppSec Research 2010 2nd cfp.png


1. Publish or Perish. Peer-reviewed 12 page papers to be published in formal proceedings by Springer-Verlag (Lecture Notes in Computer Science, LNCS). Presentation slides and video takes will be posted on the OWASP wiki after the conference.
2. Demo or Die. A demo proposal should consist of a pdf with a 1 page abstract summarizing the matter proposed by the speaker(s) and 1 page containing demo screenshot(s). Demos will have ordinary speaker slots but the speakers are expected to run a demo during the talk (live coding counts as a demo), not just a slideshow. Presentation slides and video takes will be posted on the OWASP wiki after the conference.
3. Present or Repent. A presentation proposal should consist of a 2 page extended abstract representing the essential matter proposed by the speaker(s). Presentation slides and video takes will be posted on the OWASP wiki after the conference.

If you have any questions regarding submissions etc, please email [email protected]

Topics of Interest

We encourage the publication and presentation of new tools, new methods, empirical data, novel ideas, and lessons learned in the following areas:

•    Web application security
•    Security aspects of new/emerging web technologies/paradigms (mashups, web 2.0,  offline support, etc)
•    Security in web services, REST, and service oriented architectures
•    Security in cloud-based services
•    Security of frameworks (Struts, Spring, ASP.Net MVC etc)
•    New security features in platforms or languages
•    Next-generation browser security
•    Security for the mobile web
•    Secure application development (methods, processes etc)
•    Threat modeling of applications
•    Vulnerability analysis (code review, pentest, static analysis etc)
•    Countermeasures for application vulnerabilities
•    Metrics for application security
•    Application security awareness and education

Submission Deadline and Instructions

Update: Submission deadline for full-papers ("Publish or Perish") has been extended to March 7th 23:59 (Apia, Samoa time) due to numerous requests. Submit your paper to AppSec Research 2010 (EasyChair).

Full-paper submissions should be at most 12 pages long and must be in the Springer LNCS style for "Proceedings and Other Multiauthor Volumes". Templates for preparing papers in this style for LaTeX, Word, etc can be downloaded from: http://www.springer.com/computer/lncs?SGWID=0-164-7-72376-0. Full papers must be submitted in a form suitable for anonymous review: remove author names and affiliations from the title page, and avoid explicit self-referencing in the text.

Submission for "Demo or Die" and "Present or Repent" closed on February 7th.

Decision notification: April 7th

Program Committee (for review of full-papers)

• John Wilander, Omegapoint and Linköping University (chair)
• Alan Davidson, Stockholm University/Royal Institute of Technology (co-host)
• Lieven Desmet, Katholieke Universiteit Leuven
• Úlfar Erlingsson, Reykjavík University and Microsoft Research
• Martin Johns, University of Passau
• Christoph Kern, Google
• Engin Kirda, Institute Eurecom
• Ulf Lindqvist, SRI International
• Benjamin Livshits, Microsoft Research
• Sergio Maffeis, Imperial College London
• John Mitchell, Stanford University
• William Robertson, UC Berkeley
• Andrei Sabelfeld, Chalmers UT

Call for Training (closed)

(Info kept here for reference)
OWASP is currently soliciting training proposals for the OWASP AppSec Research 2010 Conference which will take place at Stockholm University in Sweden, on June 21st through June 24th 2010. There will be training courses on June 21st and 22nd followed by plenary sessions on the 23rd and 24th with three tracks per day.

We are seeking training proposals on the following topics (in no particular order):

  • Security in Web 2.0, Web Services/XML
  • Advanced penetration testing
  • Static analysis for security
  • Threat modeling of applications
  • Secure coding practices
  • Security in J2EE/.NET patterns and frameworks
  • Application security with ESAPI
  • OWASP tools in practice

We will look favourably on laboration-based/hands-on training.

Submission Deadline and Instructions

Submission deadline is Sunday February 7th 23:59 (Apia, Samoa time). To submit your training proposal please fill out the File:OWASP AppSec Research 2010 Call for Training.docx and email it to [email protected] with subject "AppSec Research 2010: Training proposal".

Upon acceptance you'll be requested to fill out the Training Instructor Agreement where you'll find details on revenue split etc. The agreement will be reworked but the previous one is here: File:Training Instructor Agreement.doc.

Upcoming List of Trainers on OWASP Wiki

As part of the OWASP Education Project, OWASP is starting an official list of trainers on the OWASP web site. This list (mentioning the trainer - course and contact details) will cover all trainers that performed training at OWASP conferences, together with their aggregated scores on the course feedback forms. Of course, this is opt-in. Please let us know if you are interested to participate in this program (tick the check-box on the application form).

AppSec Research Challenge 9: Crack 'Em Hashes (closed)

February's AppSec Research 2010 challenge is about breaking hashed passwords. It starts off easy with the old LM hash and ends with SHA256 and GOST3411.

Owasp appsec research 2010 hash challenge.jpg

How To Win
The first one to publish each broken password gets points according to the table below but at the same time helps the others since the password is the salt of the next hash. So you have to decide -- should you publish your cracked password and collect your points before the others or should you keep it a secret to get a head start cracking the next one? Deadline it March 21st.

To collect points for a password you must be the first one to publish that broken password on this sla.ckers.org thread. Please send an email to [email protected] at the same time so we can correct any misunderstandings. For instance we can happen to run into hash collisions, where someone finds another mixed alpha password of max 5 characters that concatenated with the right salt produces the same hash. In such a case we will publish the real password and give points to the one who found the collision.

The one with the most points on March 21st wins a free ticket to the conference!

Points to Earn

  • pwd1 (LM) => 1 point
  • pwd2 (MD2) => 3 points
  • pwd3 (MD4) => 5 points
  • pwd4 (MD5) => 9 points
  • pwd5 (RIPEMD160) => 15 points
  • pwd6 (SHA1) => 25 points
  • pwd7 (SHA256) => 50 points
  • pwd8 (GOST3411) => 100 points

The Hashes
Each password comprises of a-zA-Z (mixed alpha) and is max 5 characters long. With salt that means max 10 mixed alpha characters as input to the hash function. All hashes here are in hex format. The Java source code has all the details. The plus operator means string concatenation.

  • LM(pwd1) 0C04DACA901299DBAAD3B435B51404EE
  • MD2(pwd2 + pwd1) 16189F5462BF906E9D88CF6F152DE86F
  • MD4(pwd3 + pwd2) FA8F46A6D347087D6980C3FA77DD4DE9
  • MD5(pwd4 + pwd3) 425B33D6F60394C897B8413B5C185845
  • RIPEMD160(pwd5 + pwd4) 35F34671D30472D403937820DCABC1C78C837071
  • SHA1(pwd6 + pwd5) AE81A30510B2931921934218636B26A803330EB1
  • SHA256(pwd7 + pwd6) B2FF0269E927C6559804A37590A0688C45DF143F85CEE0E3F239F846B65C9644
  • GOST3411(pwd8 + pwd7) 16CC9F1FF65688E040F5ADA82A41A258FF948769CDA4C4A17D85228A6F358971

Example: Given that pwd1 is "Win" and pwd2 is "You", the hash 16189F5462BF906E9D88CF6F152DE86F is the result of MD2("YouWin"). Now pwd2 will be the salt when you crack pwd3.

The Source Code
The source code we've used to produce the hashes is available here zip. It's Java and all but the LM hash is done with Bouncy Castle 1.4.5.


AppSec Research Challenge 8: Construct an OWASP Polyglot (closed)

January's AppSec Research Challenge is to construct an OWASP polyglot, more specifically an OWASP logo that also can be run as JavaScript:

Show image: <img src="owasp_logo.gif">
Run script: <script src="owasp_logo.gif"></script>

Wikipedia says: "a polyglot is a computer program or script written in a valid form of multiple programming languages". This is about as cool as it gets :).

Rules

  • Make your polyglot out of the regular OWASP logo in the upper left corner of this wiki (circle with the wasp).
  • The file size must not grow.
  • Pixel colors in the gif must not differ more than 5 in red, green, or blue. Ex: If a pixel originally had rgb 100,100,100 then 104,95,96 is OK.
  • No malicious stuff of course
  • When your polyglot is run as JavaScript it should execute as many of the following features as possible, starting from the top:
  1. alert(all cookies belonging to the current domain);
  2. alert(the last keystrokes on the keyboard every ten keystrokes);
  3. alert(the current time in Stockholm, once every minute);
  4. A quine. The polyglot outputs its own source code on the HTML page.

How to get started

Jasvir Nagra gave a talk on these kind of polyglots and published a gif/JavaScript polyglot on his blog. A good starting point is his gif file. Jasvir has also written an extensive article on gif/perl polyglots which explains how to get code into the gif file. Check out his guide.

How to win

Submit your entries in this sla.ckers.org thread. Either the first complete polyglot or the most complete polyglot wins. We will most probably provide you with a gif checker that validates the color differences. Check the thread. 

AppSec Research Challenge 7: X-Mas Capture the Flag (closed)

AppSec Research 2010 Stocking.gif Merry Christmas everyone!AppSec Research 2010 Stocking.gif

It's the 21st and a new AppSec Research Challenge is posted.

Setting up the AppSec Research 2010 X-mas Challenge was a cooperative effort by the winner of AppSec Research Challenge 3, Mario Heiderich, and Martin Holst Swende. It is a multi-step challenge which involves finding a vulnerability in a web application and locating a hidden message. The winner gets free entrance to next year's conference. Start by subscribing to the conference mailing list. Then check the simple rules below and get going.

Rules:

  • Please do not perform any resource-intensive tests, as the machine is pretty low-end and can be DoS:ed without much effort.
  • The computer at the given IP address is the only system involved in this challenge, so please do not perform any tests of neighboring systems.
  • Otherwise, you are free to hack away!

Challenge-page: 66.249.7.26

Discussions, QnA and reports about how far you have made it is welcome at the official sla.ckers thread.

Good luck and happy holidays! (And don't forget the submission deadline for the conference -- February 7)


AppSec Research Challenge 6: Design the Conference Logo (closed)

Note: This challenge is re-opened. Submit by February 21st.

November's AppSec Research 2010 Challenge asks you to design the conference logotype. So far we have used this:

Appsec research 2010 logo prototype (small).png

... but would like something less "word processor-like".

How to win

  • The logo should be suitable for both large printing and small web banners
  • If you make a color logo, please submit a b/w version too
  • "OWASP AppSec Research 2010" should in some way be part of the logo :)

Copyright?
By submitting your logo you agree to share it according to Creative Commons Attributions and that we credit you in the conference brochure and on the conference wiki but not in all places where we use the logo (i e we will not credit you on banners, sponsoring program, powerpoint presentations etc).

How to submit
Email jpg + svg to john.wilander [at] owasp.org before Monday December 14th 23:59 UTC. The creator of the best logo wins a free ticket to the AppSec Research 2010 conference!

AppSec Research Challenge 5: Graphical Effects (closed)

The October OWASP AppSec Research 2010 challenge is over. The winner of a free entrance ticket to next year's AppSec conference in Stockholm is "sirdarckcat" with FireworksIsNotABrowser_v4 (although we like the slightly oversized v6 better).

The challenge was about writing the coolest graphical effect in a 2010 character script.

An Example

As an example, copy the script below and paste the script over the URL in the URL bar.

javascript:R=0; x1=.1; y1=.05; x2=.25; y2=.24; x3=1.6; y3=.24; x4=300; y4=200; x5=300; y5=200; DI=document.getElementsByTagName("img"); DIL=DI.length; function A(){for(i=0; i-DIL; i++){DIS=DI[ i ].style; DIS.position='absolute'; DIS.left=(Math.sin(R*x1+i*x2+x3)*x4+x5)+"px"; DIS.top=(Math.cos(R*y1+i*y2+y3)*y4+y5)+"px"}R++}setInterval('A()',5); void(0)

As a simple teaser we give these png letters for the script to play with.

AppSec Research 2010 O.pngAppSec Research 2010 W.pngAppSec Research 2010 A.pngAppSec Research 2010 S.pngAppSec Research 2010 P.png

Rules

  • The script should work in Firefox 3.5 (yeah, that means HTML5 and CSS3 :)
  • Any resource, linked document, script, or image defined on the AppSec Research 2010 wiki page may be loaded/accessed/used
  • No requests to any other location is allowed
  • No obfuscation is allowed
  • The script may only use ASCII
  • Max length of the script is 2010 characters
  • You have to give your effect an id and a version number (further explanation below)
  • Any form of malicious code is of course banned ;)

How to Compete

There's an official thread on sla.ckers were you share your code and thoughts (Worried someone will steal you code? Check the originality bullet below). You can enter as many effects as you like but each effect has to have an id and a version number, e.g. JohnWobbler_v1.3 for version 1.3 of John's Wobbler effect. Deadline is November 14th, 23:59 UTC.

Choosing the Winner

Since this is a creative challenge the OC will choose the winner based on the following:

  • Originality (tweaking someone's code is cool and encouraged but changing a few magic numbers or inverting a function won't make you the winner)
  • Coolness (yeah, you need to convince a few Scandinavian people + Seba and Kate that your script is the coolest)

Either the OC will choose a winner by ourselves or we choose the top effects and let you guys vote for the winner.

AppSec Research Challenge 4: Who's Who in Security? (closed)

September's AppSec Research 2010 Challenge was to identify a number of people that are, in one way or another, known in the security business, by their picture. There were thirteen photos in total, portraiting thirteen different individuals.

The winner of a free ticket to the OWASP AppSec Research conference in 2010 was Thomas Vollstädt who submitted the correct solution just one day after the challenge was posted.

The Solution

Owasp appsec research 2010 challenge 4 solution.png

The Names

Dinis Cruz, Gordon "Fyodor" Lyon, David Litchfield, Dave Aitel, Bruce Schneier, Dave Wichers, Gene Spafford, MafiaBoy, MySpace Samy, Tom Brennan, Halvar Flake, Alex Sotirov, Jeff Williams, Jennifer Granick, Kate Hartmann, Mudge, Lance Spitzner, Dan Kaminsky, Brian Chess, Joanna Rutkowska, Crispin Cowan, Michael Howard, Jay Beale, Ross Anderson, Dawn Song, Robert "rsnake" Hansen, and Solar Designer.

The Pictures

If you'd like to see the original pictures without the names, here's the link: [[1]]

AppSec Research Challenge 3: Non-Alphanumeric JavaScript (closed)

The August AppSec Research 2010 Challenge was to create a JavaScript alert("owasp") that pops up the word 'owasp', case-insensitive, without using any alphanumeric characters (0-9a-zA-Z). There was a tremendous activity and we want to thank everyone who participated. The size of the final result was almost a third of the first entry (see chart below). Want to check out the winning snippet by .mario? Enter the following in the Firebug console: ω=[[Ṫ,Ŕ,,É,,Á,Ĺ,Ś,,,Ó,Ḃ]=!''+[!{}]+{}][Ś+Ó+Ŕ+Ṫ],ω()[Á+Ĺ+É+Ŕ+Ṫ](Ó+ω()[Ḃ+Ṫ+Ó+Á]('Á«)'))

It is based on a few different ideas. First of all, a variable assignment on the form

[a,b,c,,e]="abcde" // a="a", c="c",e="e"

Which is performed on the string "truefalse[object Object]"

[Ṫ,Ŕ,,É,,Á,Ĺ,Ś,,,Ó,Ḃ]=!''+[!{}]+{}] // right-hand side is "truefalse[object Object]"

Also, the following construction obtains the window.sort-function, which leaks the window-object when called without arguments :

ω=[]["sort"] //ω is now window.sort

Therefore, calling ω()["alert"] invokes window.alert. To generate the string "owasp", the string "wasp" can be obtained by calling btoa on the characters "Á«)".

This was really a great team effort, and I think a lot of us learned some new tricks. The final winner was .mario. Congratulations!

Appsec research 2010 challenge 3 chart.jpg

JavaScript Without Alphanumeric Characters?

It is possible to write valid javascript completely without alphannumeric characters (0-9a-zA-Z). To produce a number, you can instead use for example an empty string, '', interpret it as a boolean with a bang: !'' -- which leads to the boolean object true. true, interpreted as a numeric value, equals one. Thus,

$ = +!''; // $ === 1

$++;$++; // $ === 3

In a similar fashion, strings can be created from strings embedded in the language. The boolean object true can be converted to string by concatenation, and then accessed by numeric index to, for example, produce the letter 'e' :

â = (!''+'')[$] // â[$] === "true"[3] === e

Previous Similar Contest

These two techniques are behind a previous contest at the forum "sla.ckers.org", where the contest was to create alert(1) with as few non-alphanumeric characters as possible. Currently, the code actually being executed was:

([],"sort")()["alert"](1) // since ([],"sort")() leaks window object in FF, ==> window["alert"](1) is called, which is another form of window.alert(1)

The winner, or at least current leading entry is 84 bytes long, and looks like this:

(Å='',[Į=!(ĩ=!Å+Å)+{}][Į[Š=ĩ[++Å]+ĩ[Å-Å],Č=Å-~Å]+Į[Č+Č]+Š])()[Į[Å]+Į[Å+Å]+ĩ[Č]+Š](Å)

The Challenge

August's challenge was to, in a similar fashion, create an alert("owasp"), case-insensitive, not using any alphanumeric characters. The shortest working code snippet submitted by September 18th 23:59:59 UTC won a free ticket. By "working" we meant JavaScript that executes in Firefox/Firebug, not depending on any Firebug DOM variables for execution.

Submissions were made as comments to the challenge 3 blogpost on Owasp Sweden. Check it out.

AppSec Research Challenge 2: OWASP Crossword Puzzle (closed)

July's crossword challenge is over. Many permutations arrived in our inbox but it was tricky to get it completely right. Congratulations to Johannes Dahse and Johan Nilsson who in the end were allowed to join forces to be able to find the correct solution. They win a 50 % conference ticket discount each.

You find the solution below.

Appsec research 2010 challenge 2 solution.gif

AppSec Research Challenge 1: Input Validation and Regular Expressions (closed)

This challenge is over. The winner was Partik Nordlén. To see the solution(s), please visit the appsec_eu_2010 mailing list archive.

Some people, when confronted with a problem, think “I know, I'll use regular expressions.” Now they have two problems.
        --Jamie Zawinski, in comp.emacs.xemacs

The 21st of each month up until the conference in June 2010 we'll have a countdown challenge posted here. The winner each month will get a free entrance ticket worth about €300/$400. Be sure to sign up for the conference mailing list to get a monthly reminder.

The Challenge

A community is hosted on a very large domain, yahoogle.com. The users of that community all have profiles, where they are allowed to use basic HTML for customization, as well as JavaScript files hosted on the domain.

All the code for the profile pages are filtered on the server side, and whenever a piece of code containing "<script..." is encountered, the following regular expression is used to validate that the script loaded is hosted on a subdomain of yahoogle.com:

.*(<script){1}([^>]+)src=('http:\/\/[a-zA-Z]+.yahoogle.com\/scripts\/[0-9A-Za-z]+\.js').*\/>

Capture group 3 is then also checked against a whitelist of allowed scripts on that domain. The whitelist consists of "http://secure.yahoogle.com" and "http://scripts.yahoogle.com".

Your task is to formulate a snippet of HTML that goes correctly through the filter and the whitelist, but loads the script "http://insecure.com/evil.js" instead. Also, rework the regular expression to defend against your "attack".

Email your solution to Martin Holst Swende <[email protected]>. The first correct answer wins a free ticket to the conference. The free ticket is personal and the judgement of the organizing committee can not be overruled :).