Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Shiny, Let's Be Bad Guys: Exploiting and Mitigating the Top 10 Web App Vulnerabilities -- 2014 edition

Shiny, Let's Be Bad Guys: Exploiting and Mitigating the Top 10 Web App Vulnerabilities -- 2014 edition

Slides from the Pycon 2014 presentation of our tutorial that walks through the OWASP Top 10 web application vulnerabilities.


Mike Pirnat

April 10, 2014


  1. Shiny Text Let’s Be Bad Guys! Exploiting and Mitigating the

    Top 1 0 Web App Vulnerabilities Mike Pirnat David Stanek - @mpirnat - @dstanek
  2. Announcements

  3. Schedule • This session will run 1:20 PM - 4:40

    PM • 20-minute break at 3:30 PM
  4. Volunteering Opportunities • Low-commitment! Fun! • SWAG bagging: Thursday 3-7

    PM • Exhibit Hall 220C – 2nd floor of conference center • Just do 10 bags! (~1/2 hr) • Registration Desk: any time • 1-2 hours helps • Friday => meet everyone!
  5. Tutorial Feedback • Go here: • https://www.surveymonkey.com/s/ pycon2014_tutorials or •

    http://goo.gl/Ppq8yR • Be honest!
  6. None
  7. Shiny Text Let’s Be Bad Guys! Exploiting and Mitigating the

    Top 1 0 Web App Vulnerabilities Mike Pirnat David Stanek - @mpirnat - @dstanek
  8. http://i.qkme.me/3r16r5.jpg

  9. Who here makes web apps?

  10. Who here has vulnerable apps?

  11. Why it Matters • Your users • Your data •

    Your business
  12. OWASP • http://www.owasp.org • Open Web Application Security Project •

    Non-profit focused on improving software security • Documentation and tools to help learn about security and protect your apps
  13. OWASP Top Ten • Based on risk data from 8

    firms • Over 500,000 vulnerabilities, hundreds of orgs, thousands of apps • Selected & prioritized by prevalence data combined with estimates of exploitability, detectability, and impact • Updated in 2013
  14. Today • Background on a type of vulnerability • Exploit

    it! • Discuss prevention • Django-specific advice where possible • Light examples where we have time
  15. Disclaimer

  16. About Django

  17. Setup: 1 Make a virtualenv: $ virtualenv badguys $ cd

    badguys $ source bin/activate
  18. Setup: 2 Clone our repository: $ git clone https://github.com/ mpirnat/lets-be-bad-guys

    src Or pull the latest changes: $ cd src $ git pull
  19. Setup: 3 Install dependencies: $ cd src $ pip install

    -r requirements.txt
  20. Setup: 2 & 3 (Offline/USB) • Extract the project: $

    mkdir src $ unzip /Volumes/BADGUYS/project/ badguys.zip -d src/ • Install dependencies: $ cd src $ pip install -r requirements.txt -i file:///Volumes/BADGUYS/software
  21. Setup: 4 Start up the app: $ python manage.py runserver

  22. Find a Partner

  23. Injection

  24. Injection Attacks • When an application sends untrusted data to

    an interpreter • Can result in data loss/corruption, lack of accountability, denial of access • Can lead to complete host takeover
  25. Trust No One • External users • Internal users •

  26. Attack Vectors • GET parameters • POST parameters • PATH_INFO

    • Some HTTP headers: Cookie, Host • Uploaded Files
  27. Possible Consequences • Creation of malicious SQL (or other queries)

    • Accessing private files on disk • Arbitrary code execution
  28. Real-World Examples • Sony Playstation Network • Ruby on Rails

    • http://es.pn/Z0jnoi
  29. SQL Injection • Unescaped user input causes the premature end

    of a SQL query and allows a malicious query to be executed... """ select * from users where username='%s'; """ • http://localhost:8000/injection/sql
  30. Accessing Private Files • File system access + unvalidated user

    input allows attackers to navigate the file system • http://localhost:8000/injection/file- access
  31. Arbitrary Code Execution • Unsafe input is dynamically evaluated or

    executed • http://localhost:8000/injection/code- execution
  32. Prevention • Validate ALL user input • Sign cookies, don’t

    accept if signature is bogus/missing • Use ORMs or bind variables when talking to the database • Don’t use eval or exec, beware of pickle, user-supplied YAML, etc.
  33. Django Advice • Make sure data types for your model

    are tight • Use Forms instead of ModelForms for stronger validation • Make new validators as needed for your application • Make sure your URL regexes for dynamic URLs are tight
  34. Django Advice • Use the ORM when you can •

    When you can’t, use extreme caution! • Bind variables • No string concatenation/formatting of anything that came from the client
  35. Without the ORM # If it's a basic select: MyModel.objects.raw("SELECT

    ... WHERE foo = %s", params={'foo': ...}) # If it's more complicated: from django.db import connection cursor = connection.cursor() cursor.execute("UPDATE bar set bar = 1 WHERE foo < %s", [foo]) row = cursor.fetchall()
  36. Broken Authentication & Session Management

  37. Broken Auth & Session Management • Attacker uses leaks or

    flaws in authentication or session management to impersonate users • Roll-your-own solutions contribute to the difficulty of finding these flaws
  38. Possible Consequences • Compromised user accounts • Compromised administrative accounts

    • Unauthorized use of privileged functionality
  39. Prevention • Hash or encrypt passwords • Don’t let credentials

    be easily overwritten • Don’t put session IDs in URLs • Allow session IDs to timeout/log out • Rotate session IDs after successful login • TLS connections for passwords, session IDs
  40. Django Advice • Use django.contrib.auth • Consider https://github.com/yourlabs/ django-session-security middleware

    for timing out sessions • We’ll talk about transport layer security later on...
  41. Cross-Site Scripting (XSS)

  42. XSS Attacks • Cross-Site Scripting (XSS) • The most prevalent

    web app security flaw • App includes user-supplied data in content sent to the browser without properly validating or sanitizing it
  43. XSS Attacks • Stored: injected code permanently stored in database,

    message forum, comment, etc. • Reflected: injected code in live request to server, reflected back in error message or search result • DOM: injected code in browser DOM environment that causes scripts to run in unexpected ways (eg, reading from URL)
  44. Possible Consequences • Execute scripts in a victim’s browser •

    Hijack sessions • Deface sites • Insert hostile content • Redirect users • Hijack browser (install malware)
  45. Most Often Seen... • Places where user-created text is displayed

    to other users (comments, messages) • Form inputs where value is populated with user-supplied data • Script tags where user-supplied data is populated into script variables
  46. XSS in Dynamic URLs • Part of the URL path

    is variable, isn’t validated, and gets included into the page • http://localhost:8000/cross-site- scripting/path-matching/your-path- here
  47. XSS in Query String Parameters • Unvalidated user input from

    a query string parameter is included in the page • http://localhost:8000/cross-site- scripting/query-params?qs=awesome
  48. XSS in Form Fields • The value part of an

    input is prematurely terminated, allowing Javascript to be injected into the element (eg, adding an onclick) • http://localhost:8000/cross-site- scripting/form-field
  49. Can you trust the database?

  50. Prevention • Escape all untrusted data based on the HTML

    context the data will be placed into • Whitelist input validation • Consider auto-sanitization libraries for rich content (eg, OWASP’s AntiSamy) • Update your parents’/in-laws’ browsers!
  51. Django Advice • Be careful with the safe filter, django.utils.safestring,

    etc. • Use form.as_p, form.as_table, form.as_ul when displaying a form in a template • Be careful with your own template tags; django.utils.html.escape is your friend!
  52. django.utils.html cleaned = escape(unsafe_value) cleaned = escapejs(unsafe_value) cleaned = strip_tags(unsafe_value)

    cleaned = remove_tags(unsafe_value, ['script', ...])
  53. Insecure Direct Object References

  54. Insecure Direct Object Reference • Expose a reference to an

    internal implementation object without verifying authorization • Attacker changes URL or GET/POST parameters, cookies
  55. Possible Consequences • Compromise of all data that can be

    referenced by the vulnerable parameter • Unless the namespace is sparse, an attacker can easily access all available data of that type
  56. Exercises • Manipulate parameters in the URL to access data

    that doesn’t belong to you • http://localhost:8000/direct-object- references
  57. Prevention • Implement access controls on any direct references to

    restricted resources • Implement per-user or per-session indirect object references
  58. Django Advice • Use permissions architecture to lock down views

    • Customize queryset for looking up objects that involve user ownership
  59. Custom Queryset # In models.py... class ThingyManager(models.Manager): def for_user(self, user):

    return self.get_query_set().filter(user=user) class Thingy(models.Model): objects = ThingyManager() # In views.py... class ThingyUpdateView(UpdateView): def get_queryset(self): return Thingy.objects.for_user( self.request.user)
  60. Security Misconfiguration

  61. Security Misconfiguration • Insecure application settings • Unpatched flaws •

    Unused pages
  62. Possible Consequences • Unauthorized access to some system data or

    functionality • Potential complete system compromise
  63. Exercises • Demos and discussion • http://localhost:8000/misconfiguration

  64. Prevention • Have a repeatable hardening process • Have a

    process for keeping on top of updates and patches • Architecture that provides secure separation between components • Periodic scans and audits
  65. Django Advice • Don’t run in debug mode in production

    • Keep your SECRET_KEY secret! • Keep Python code out of webserver’s root • Don’t run admin publicly (if you can help it) • Don’t use the built-in admin for normal user admin tasks
  66. Gateway to Social Engineering?

  67. Sensitive Data Exposure

  68. Sensitive Data Exposure • Failure to properly protect credit cards,

    tax ids, authentication credentials, etc. • Sensitive data deserves extra protection such as encryption at rest or in transit, special precautions when exchanged with the browser
  69. Insecure Cryptographic Storage • Not encrypting worthy data • Unsafe

    key generation & storage, failure to rotate keys • Weak algorithms • Weak or unsalted hashes
  70. Insufficient Transport Layer Protection • May not authenticate, encrypt, and

    protect the confidentiality and integrity of sensitive network traffic • May use weak algorithms • May use expired or invalid certificates • May use certificates incorrectly
  71. Possible Consequences • Compromise of all data that should have

    been encrypted • This can be highly sensitive information: credentials, credit cards, personal data, health records, etc.
  72. Possible Consequences • Expose individual users’ data • Account theft

    • Compromise an admin account?! • Poor SSL setup can facilitate phishing and man-in-the-middle attacks
  73. Attack Vectors • Attacker monitors network traffic of your users

    • Maybe in public places (Starbucks, conference wi-fi, etc.) • Maybe back end connections • Maybe inside your network (!!!)
  74. Prevention • Encrypt sensitive data at rest • Encrypt offsite

    backups; manage keys separately • Use strong standard algorithms, strong keys • Hash passwords with strong standard algorithm & use appropriate salt • Protect passwords & keys from unauthorized access
  75. Prevention • Require SSL for all sensitive pages; redirect non-SSL

    requests to SSL • Set the “secure” flag on sensitive cookies • Use only strong SSL algorithms • Ensure your cert is valid, not expired, not revoked, and matches your domain • SSL/encryption on the back end too
  76. Django Advice • Use django.contrib.auth for proper password salting and

    hashing • Require SSL in Apache or Nginx • Require SSL using middleware: • https://github.com/rdegges/django-sslify • http://www.redrobotstudios.com/blog/2010/02/06/ requiring-https-for-certain-paths-in-django/ • http://djangosnippets.org/snippets/2833/ • http://djangosnippets.org/snippets/1467/
  77. Secure Cookies # In your settings.py... SESSION_COOKIE_SECURE = True CSRF_COOKIE_SECURE

    = True
  78. Missing Function Level Access Control

  79. Missing Function Level Access Control • Application doesn’t protect its

    functions properly • Misconfiguration • Forgot proper code checks
  80. Attack Vectors • Authorized user changes a URL or parameter

    to a privileged function • Anonymous users could access private functions that aren’t protected
  81. Possible Consequences • Compromised user accounts • Compromised administrative accounts

    • Unauthorized use of privileged functionality
  82. Exercises • Manipulate the URL to access privileged functionality •

    http://localhost:8000/missing-access- control
  83. Prevention • Consider every page; public or private? • If

    authentication is required, make sure that checks are in place • If additional authorization is required, make sure that checks are in place • Deny all by default; explicitly grant access to users or roles
  84. Django Advice • Use the permissions architecture to lock down

    views • Don’t use the built-in admin for normal user admin tasks
  85. Cross-Site Request Forgery

  86. CSRF Attacks • Cross-Site Request Forgery (CSRF) • Attacker tricks

    victim into submitting forged HTTP requests • Attack succeeds if user is authorized/ authenticated
  87. Attack Vectors • Image tags • Cross-Site Scripting (XSS) •

    Fake buttons • Phishing forms • Other techniques
  88. Possible Consequences • Cause victim to change any data the

    victim is allowed to change • Cause victim to perform any function the victim is authorized to use • Impact varies based on victim’s role • Think of some possibilities...
  89. Real-World Examples • Facebook: http://amolnaik4.blogspot.com/ 2012/08/facebook-csrf-worth- usd-5000.html • Google/Gmail: http://cryptogasm.com/2012/02/does-

  90. CSRF via Image • Craft an “image” link that triggers

    some site functionality • http://localhost:8000/csrf/image
  91. What if... <img src="http://example.com/transferFunds?amount=1500& destinationAccount=attackersAcct#" width="0" height="0" />

  92. CSRF via Form Post • Create an innocuous-looking form that

    POSTs to a vulnerable location • http://localhost:8000/csrf/third-party- site
  93. Prevention • Don’t “do” things on a GET • Include

    a unique token in a hidden field (often used in concert with a cookie) • Validate token to make sure the request is from on-site • Avoid putting the token into a query string
  94. Django Advice • Don’t change the built-in settings! • Do

    use the CSRF middleware and template tag in forms • Be VERY CAREFUL about deactivating it (csrf_exempt decorator) • Be careful about APIs (Tastypie, oauth); http://codrspace.com/vote539/csrf- protection-in-django-tastypie/
  95. Using Known Vulnerable Components

  96. Components with Known Vulnerabilities • Libraries, frameworks, and other modules

    almost always run with full privilege • Hard to stay up to date on everything • Do you even know all the components in use, let alone their versions? • Components with known problems can be identified & exploited with automated tools
  97. Attack Vectors • Attacker identifies a weak component through scanning

    or manual analysis • Customize exploit as needed • More difficult the deeper the component is in the application
  98. Possible Consequences • Full range of weaknesses are possible •

    Impact could be minimal, or... • Complete host takeover! • Data compromise!
  99. None
  100. Prevention • Don’t use components you don’t write (unrealistic) •

    Keep components up to date • Identify all components and versions • Monitor security of these components
  101. Django Advice When @djangoproject says there are new security releases

    for Django, upgrade!
  102. Unvalidated Redirects & Forwards

  103. Redirection Abuse • Attacker tricks user into visiting a URL

    that redirects or forwards the request without validating the redirect location • Users prone to click because the link is to a legitimate site
  104. Possible Consequences • Install malware • Phishing/information disclosure • Bypass

    access controls
  105. External Redirection • Use a redirection URL to redirect to

    an external location • http://localhost:8000/redirects-and- forwards/redirects
  106. Forwards • Manipulate a forward parameter to gain access to

    privileged functionality • http://localhost:8000/redirects-and- forwards/forwards
  107. Prevention • Don’t use redirects or forwards • Don’t involve

    user-supplied data to build the redirect location • Ensure the supplied value is valid and authorized for the user
  108. Django Advice • Use django.utils.http.is_safe_url to check redirect URLs •

    Used by django.contrib.auth internally • Consider wrapping is_safe_url if you have to allow other off-domain URLs
  109. Checking Redirects from django.shortcuts import redirect from django.utils.http import is_safe_url

    def my_view(request): ... url = 'http://www.example.com/foo/bar' if is_safe_url(url, host='www.example.com'): return redirect(url) else: ...
  110. Allowing Multiple Safe Hosts from django.utils.http import is_safe_url def is_whitelisted_url(url,

    hosts): for host in hosts: if is_safe_url(url, host=host): return True return False >>> url = 'http://us.pycon.org' >>> whitelist = ['us.pycon.org', 'pycon.org', ...] >>> is_whitelisted_url(url, whitelist) True
  111. Who here has vulnerable apps?

  112. Parting Thoughts

  113. Think Like a Bad Guy

  114. Don’t Stop at Ten

  115. Constant Change

  116. Think Positive

  117. Announcements • Feedback—http://goo.gl/Ppq8yR • Volunteer! • Heartbleed

  118. Links • http://www.owasp.org • https://www.owasp.org/index.php/ Category:OWASP_Top_Ten_Project • https://docs.djangoproject.com/en/dev/ topics/security/ •

  119. Contact Us Mike Pirnat http://mike.pirnat.com @mpirnat David Stanek http://traceback.org @dstanek