駭客看 Django

Taiwan Python Conference 2013

Transcript

1. 駭客看 DJANGO 2013/05/26 @ PyCon <Orange@chroot.org>
2. 本場演講「四不一沒有」
3. 四不一沒有 •  四不 – 我不是駭客 – 我不會寫 django – 不會有 django 新漏洞（ 請洽七月台灣駭客年會 ） – 這場演講不難，真的很簡單 •  沒有 – 這場演講沒有梗，有笑點的話拜託笑一下
4. About Me •  蔡政達 aka Orange •  2009 台灣駭客年會競賽 冠軍 •  2011, 2012 全國資安競賽 金盾獎冠軍 •  2011 東京 AVTOKYO 講師 •  2012 香港 VXRLConf 講師 •  台灣 PHPConf, WebConf 講 師 •  專精於 –  駭客攻擊手法 –  Web Security –  Windows Vulnerability Exploitation
5. About Me •  CHROOT Security Group 成員 •  NISRA 資訊安全研究會 成員 •  Disclosed – Windows MS12-071(CVE-2012-4775) – Django (CVE-2013-0305) •  Blog – http://blog.orange.tw/
6. 2013 年 X 月 O 日 天氣晴，今天是寒假的第一天… 幹, Rails 爆遠端執行代碼漏洞欸
8. Django 會不會有同樣的問題呢？ 學生什麼都沒有， 最多的就是時間。 來研究個 Open Source 專案很正常吧！
9. Vulnerabilities by Year Django
10. Vulnerabilities by Year Django 同樣情境跟 Rails 比較...
11. 包含至少 8 個 Remote Code Execution
12. ......
13. 其實我今天是來推廣 Rails 開玩笑的啦我沒有要戰語言 T＿T
14. Django 現有的保護機制 Django Security Overview
15. Security Overview •  Built-in XSS protection •  Built-in SQL Injection protection – ORM ( Q Object ) •  Built-in CSRF protection – django.middleware.csrf.CsrfViewMiddleware – Check REFERER header – Compare CSRF token
16. Security Overview •  Clickjacking protection – django.middleware.clickjacking.XFrameOptionsMiddleware – Optional in settings.py – X-Frame-Options: SAMEORIGIN
17. Security Overview •  Password hashing is more and more stronger – Default is PBKDF2 hasher – django.contrib.auth.hahsers – 10000 iterators makes attackers say fuck … $ time python pbkdf2.py mypassword real 0m0.401s user 0m0.260s sys 0m0.074s
18. 攻擊手法 Some Attacking Vectors
19. Some Attacking Vectors •  VERY VERY BASIC attacking way •  Weak admin password •  Debug mode on – Leakage URL pattern – Leakage database password
20. Some Attacking Vectors •  Cross-Site Scripting – HttpResponse( html ) – {{ output|safe }} – {% autoescape off %} •  Bad HTML style is always vulnerable – <a href="{{ url }}"> # safe – <a href={{ url }}> # unsafe – <a href=xxx onload=alert(/xss/)>
21. Some Attacking Vectors •  SQL Injection in Django ORM – raw( sql ) is injectable – extra( select=…, where=… ) is also injectable •  String concatenate and format string are vulnerable in any case
22. Some Attacking Vectors •  Third-party module security •  Py-bcrypt # CVE-2013-1895 – Authentication bypass •  Python Image Library # CVE-2012-3443 – Denied-of-Service •  Python XML.sax # CVE-2013-1664 & 1665 – XXE & XEE Injection
23. XML eXternal Entity Injection Parsing XML Document Type Definition issue <?xml encoding='utf-8' ?> <!DOCTYPE account[ <!ENTITY output SYSTEM '/etc/passwd'>]> <account> &output; </account>
24. XML Entity Expansion Injection <?xml encoding='utf-8' ?> <!DOCTYPE account[ <!ENTITY a "ooo"> <!ENTITY b "&a; &a; &a; &a; &a;"> <!ENTITY c "&b; &b; &b; &b; &b;"> ... <!ENTITY z "&y; &y; &y; &y; &y;"> ]> <account> &z; </account>
25. Secret Key Leakage Issue (1/3) •  Django SECRET_KEY use in – get_random_string() using in csrf and hash generating – Django session_data encryption – Django signed cookie encryption – ……
26. Secret Key Leakage Issue (2/3) •  Signed cookie store python object using Pickle – > HTTP_COOKIE – > decode with secret_key – > pickle.loads( … )
27. Pickle & cPickle •  A module that serializing and De-serializing python objects •  Execute command >>> import pickle >>> pickle.loads( "cos\nsystem\n(S'/bin/sh'\ntR." ) •  You can observe by using pickletools >>> import pickletools >>> pickletools.dis( "cos\nsystem\n(S'/bin/sh'\ntR." )
28. Secret Key Leakage Issue (3/3) •  Signed_cookie is encoded by Pickle – > HTTP_COOKIE # malicious cookie – > decode with secret_key – > pickle.loads( … ) # code execution •  Protect your SECRET_KEY ( ex .gitignore )
29. Conclusion •  I think Django is a secure framework •  More and more wrapper make the attack difficult •  People is always the most dangerous things
30. Reference •  Django Weblog – https://www.djangoproject.com/weblog/ •  Security in Django – https://docs.djangoproject.com/en/dev/topics/security/ •  CVE Details – http://www.cvedetails.com/
31. Any Questions ? Whatever can be asked
32. Thanks. <Orange@chroot.org>