Web Servislerinin Hacklenmesi, Ömer Çıtak

24
Web Servislerinin Hacklenmesi Ömer Çıtak XIII. BiLMÖK, 2017

Transcript of Web Servislerinin Hacklenmesi, Ömer Çıtak

Page 1: Web Servislerinin Hacklenmesi, Ömer Çıtak

Web Servislerinin Hacklenmesi

Ömer ÇıtakXIII. BiLMÖK, 2017

Page 2: Web Servislerinin Hacklenmesi, Ömer Çıtak

whoami

Security Researcher @ Netsparker Ltd.

Developer @ Another Times

Writer @ Ethical Hacking “Offensive & Defensive” Book

Blog: omercitak.com

All Social Platform: @Om3rCitak

Page 3: Web Servislerinin Hacklenmesi, Ömer Çıtak

http

Page 4: Web Servislerinin Hacklenmesi, Ömer Çıtak

?

Page 5: Web Servislerinin Hacklenmesi, Ömer Çıtak

apple

Page 6: Web Servislerinin Hacklenmesi, Ömer Çıtak

http web service

Page 7: Web Servislerinin Hacklenmesi, Ömer Çıtak

vocabulary

● API => Application Programing Interface

Page 8: Web Servislerinin Hacklenmesi, Ömer Çıtak

vocabulary

● API => Application Programing Interface● REST => REpresentational State Transfer

Page 9: Web Servislerinin Hacklenmesi, Ömer Çıtak

vocabulary

● API => Application Programing Interface● REST => REpresentational State Transfer● RESTful => REpresentational State Transfer ful

Page 10: Web Servislerinin Hacklenmesi, Ömer Çıtak

vocabulary

● API => Application Programing Interface● REST => REpresentational State Transfer● RESTful => REpresentational State Transfer ful● GET, POST, PATCH/PUT, OPTIONS, DELETE

Page 11: Web Servislerinin Hacklenmesi, Ömer Çıtak

vocabulary

● API => Application Programing Interface● REST => REpresentational State Transfer● RESTful => REpresentational State Transfer ful● GET, POST, PATCH/PUT, OPTIONS, DELETE● Route

Page 12: Web Servislerinin Hacklenmesi, Ömer Çıtak

vocabulary

● API => Application Programing Interface● REST => REpresentational State Transfer● RESTful => REpresentational State Transfer ful● GET, POST, PATCH/PUT, OPTIONS, DELETE● Route● Basic Authentication

Page 13: Web Servislerinin Hacklenmesi, Ömer Çıtak

vocabulary

● API => Application Programing Interface● REST => REpresentational State Transfer● RESTful => REpresentational State Transfer ful● GET, POST, PATCH/PUT, OPTIONS, DELETE● Route● Basic Authentication● 200, 201, 400, 401 etc...

Page 14: Web Servislerinin Hacklenmesi, Ömer Çıtak

vocabulary

● API => Application Programing Interface● REST => REpresentational State Transfer● RESTful => REpresentational State Transfer ful● GET, POST, PATCH/PUT, OPTIONS, DELETE● Route● Basic Authentication● 200, 201, 400, 401 etc…● Proxy

Page 15: Web Servislerinin Hacklenmesi, Ömer Çıtak

restful routes

Page 16: Web Servislerinin Hacklenmesi, Ömer Çıtak

OWASP Mobile Top 10

1. Improper Platform Usage2. Insecure Data Storage3. Insecure Communication4. Insecure Authentication5. Insufficient Cryptography6. Insecure Authorization7. Client Code Quality8. Code Tampering9. Reverse Engineering

10. Extraneous Functionality

Page 17: Web Servislerinin Hacklenmesi, Ömer Çıtak

OWASP Mobile Top 10

Insecure Data Storage

This new category is a combination of M2 + M4 from Mobile Top Ten 2014. This covers insecure data storage and unintended data leakage.

Page 18: Web Servislerinin Hacklenmesi, Ömer Çıtak

OWASP Mobile Top 10

Insecure Communication

This covers poor handshaking, incorrect SSL versions, weak negotiation, cleartext communication of sensitive assets, etc.

Page 19: Web Servislerinin Hacklenmesi, Ömer Çıtak

OWASP Mobile Top 10

Insecure Authentication

This category captures notions of authenticating the end user or bad session management. This can include:

● Failing to identify the user at all when that should be required● Failure to maintain the user's identity when it is required● Weaknesses in session management

Page 20: Web Servislerinin Hacklenmesi, Ömer Çıtak

OWASP Mobile Top 10

Insufficient Cryptography

The code applies cryptography to a sensitive information asset. However, the cryptography is insufficient in some way. Note that anything and everything related to TLS or SSL goes in M3. Also, if the app fails to use cryptography at all when it should, that probably belongs in M2. This category is for issues where cryptography was attempted, but it wasn't done correctly.

Page 21: Web Servislerinin Hacklenmesi, Ömer Çıtak

OWASP Mobile Top 10

Insecure Authorization

This is a category to capture any failures in authorization (e.g., authorization decisions in the client side, forced browsing, etc.). It is distinct from authentication issues (e.g., device enrolment, user identification, etc.).

Page 22: Web Servislerinin Hacklenmesi, Ömer Çıtak

demo

Page 23: Web Servislerinin Hacklenmesi, Ömer Çıtak

where is the güvenlik?

Page 24: Web Servislerinin Hacklenmesi, Ömer Çıtak

thanks

www.omercitak.com

All Social Platform: @Om3rCitak