Your SlideShare is downloading. ×
Web application security   qa2010
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

Web application security qa2010

333
views

Published on

Published in: Education

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
333
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Although the number of vulnerabilities affecting Web applications has grown at a staggering rate, the growth demonstrated in the first half of 2009 and continuing through the second half may indicate the start of a plateau, at least in standard (off-the-shelf) software applications for the Web. These figures do not include custom-developed Web applications or customized versions of these standard packages, which also introduce vulnerabilities.
  • The lecture is devided into two parts, a theoretical part and a practical part. We will begin with a few 101 and then go deep into the demos
  • A very Important restriction is that a JavaScript code origin from one domain could not see any data origin from a different domain. This restriction is called “Same Origin Policy” and was made to protect against a unwanted data sharing between two sites. Think of a scenario where an attacker creates a site with a script in it that “looks” at another browser’s window. The other window might contain the victim’s personal data (bank account details, for example). Same Origin Policy restricts the information coming from each domain to that domain only. Mainly, a script which is running on one domain cannot gain any data that comes from another domain.
  • Cross-Site Scripting is one of the most common security vulnerabilities. It happens when user input (such as HTTP params) is printed back to the response. When this is the case, an attacker can make a website to return an arbitrary JavaScript which may do malicious actions. One attack scenario would be to convince the victim to click on a link which exploits a vulnerable application
  • Let’s take a look at the chain of events during a XSS attack The attack creates and sends the victim a link to bank.com (a trusted site). The link contains a search string (or any other string that is echoed back), which contains a malicious JavaScript code The victim, clicks on this link, since he/she trusts the bank.com web site The bank.com web application, echoes back the malicious JavaScript code inside the response page. This JavaScript is executed in the security context of bank.com, since it is echoed by from that site. This means that it has access to DOM elements belonging to this domain/session The malicious script, sends the current cookie and session information, without the victim’s consent, to the evil.org web site, where the hacker is waiting for it.
  • If a hacker can get you to run a JavaScript, he/she can: - Steal your cookies for the domain you’re browsing - Completely modify the content of any page you see on this domain - Track every action you do in that browser from now on - Redirect you to a Phishing site - Exploit browser vulnerabilities to take over machine XSS is currently one of the “hottest” security risks
  • Transcript

    • 1. Web Application Security What hackers are doing with your bugs Adi Sharabani IBM Rational Security Strategist IBM Master Inventor
    • 2. About Me
      • My name is Adi Sharabani
      • Security Strategist for IBM Rational
      • Used to manage the Rational Application Security Research
      • 15 years of experience in Security
      • OWASP IL Committee
      • Application Security Insider Blog: http://blog.watchfire.com
      • Also, very proud to be a teacher in Ohel Shem, Ramat Gan
    • 3. Web App Vulnerabilities Continue to Dominate
        • 55% of all vulnerabilities are Web application vulnerabilities.
        • Cross-Site Scripting & SQL injection vulnerabilities continue to dominate.
    • 4. Agenda
      • Theoretical part:
        • Same Origin Policy
        • Cross-Site Scripting
      • Practical part:
        • Demonstrating a real attack
    • 5. Browser Scripting Capabilities
      • What can scripts do:
        • Scripts can perform user interactions with the site
        • Scripts can seamlessly interact with the web site
        • Can perform any action that is related to the site
        • Can launch signed and safe ActiveX control
    • 6. Scripting Restrictions – Same Origin Policy
      • What scripts can not do:
        • Scripts can only interact with the domain they came from
        • Scripts can see send and receive responses only from their own domain
        • Scripts can access other browser’s frames only from same domain
        • Scripts can issue requests to other domains (but cannot view the corresponding responses )
      a.com b.com a.com
    • 7. XSS 101
      • XSS occurs when user input (JavaScript) is returned by the web application as is:
      • Simple exploit:
        • http://www.thebank.site/action?param= <script>...</script>
      • Result:
        • Injected script returned by the server and executed by the victim’s browser
      • XSS breaks Same-Origin Policy
        • Vulnerable domain may now return arbitrary JavaScripts
        • String data = request.getParameter(“param”);
        • out.println(data)
    • 8. Cross Site Scripting – The Exploit Process Evil.org TheBank.site User Script returned, executed by browser 3 User sends script embedded as data 2 1 Link to bank.com sent to user via E-mail or HTTP
    • 9. Exploiting XSS
      • If I can get you to run my JavaScript, I can…
        • Steal your cookies for the domain you’re browsing
        • Completely modify the content of any page you see on this domain
        • Track every action you do in that browser from now on
        • Redirect you to a Phishing site
        • Exploit browser vulnerabilities to take over your machine
      • XSS is one of the Top Web Security Risk today (most exploited)
    • 10. Demo
    • 11. There are solutions for this!
      • Education:
        • Secure coding for developers
        • Security testing for QA
      • Tools:
        • Such as Rational AppScan (both blackbox and whitebox)
      • Development process:
        • Integration into the development lifecycle
    • 12. ? [email_address] http:// blog.watchfire.com