1. internet security
Past, present and future
Tamaghna Basu
tamaghna.basu@gmail.com
www.tbasu.com

2. Weekendsecurity.org

3. Disclaimer!
 The content of this presentation and techniques showed
here are for educational purpose only The organizers and
presenters do not encourage the attendees to use this
knowledge learned here for any malicious and illegal
purpose.
 If the attendees use this knowledge for any kind of real
hacking or illegal activity which violates the law, then we,
the organizers and the presenters will not be responsible for
that or any further consequences.

4. http://www.slideshare.net/AnkamKarthik/zion-se

5. http://www.slideshare.net/AnkamKarthik/zion-se

8.  Confidentiality- data security
 Integrity- digital signature and audit trails
 Availability- load balancing, throttling
CIA Triad
Integrity

9. You are being watched - CCTV
•Weak or no authentication on
CCTVs
•Easily accessible

10. CCTV
How ?
• IP addresses and the links of the
CCTVs’ pages are found in
Google search results.
• Even CCTVs inside homes
could be visible.

11. CCTV

12. Web Cams &Video Chat
Clickjacking -
 A new threat to all browsers (IE, Firefox,
Safari, Opera, Chrome etc) except non-
interactive browsers like Lynx.
 Hijacking your click. Clicking on something
hidden to the users.
 Enable webcam, microphone.
 Get your credentials.
 Mostly a flash and iframe based vulnerability.
 Discussed in OWASP - 2008

13. Why Hacking?
 Hacking for fun & profit
 Capture The Flag
 0’day
 Underground economy
 Bug Bounty

14. Types of hackers
BlackHat
•Malicious, destructive
WhiteHat
•Security professionals
ScriptKiddie
•Sometimes referred to as n00bz
????

15. Hacktivism
Anonymous
Wiki Leaks
CyberWar
India-Pakistan
India-China
Pivoting

16. What do they want?
Credentials
PII information
PCI Data
Intellectual Property
OSINT

18. Why heart bleed?
 TLS HearBeat Extension.
The vulnerability lies in the implementation of TLS
Heartbeat extension. There is common necessity
in an established ssl session to maintain the
connection for a longer time. The HeartBeat
protocol extension is added to TLS for this reason.
The HTTP keep-alive feature does the same but HB
protocol allows a client to perform this action in
much higher rate.
The client can send a Heart-Beat request message
and the server has to respond back with a
HearBeat response .

19. Why heart bleed?
 buffer = OPENSSL_malloc(1 + 2 + payload +
padding);
SOURCE :
https://github.com/openssl/openssl/commit/96db9023b881d7cd9f3
79b0c154650d6c108e9a3#diff-2

20. • We can leak 64 kb of memory and that
could easily have usernames/password,
private keys etc.
• Constant HB request could be made to
the server leaking (random memory)
any amount of data from the server .

21. Vulnerable versions

22. Fix
• The fix to this bug was to simply bound
check the payload + padding length to
not exceed 16 bytes .

23. What’s happening in the wild?

24. What’s happening in the wild?

28. Chromebleed

29. chromebleed

30. And My contribution as well 

33. Is that all?

34. Not really…
http://filippo.io/Heartbleed/

39. Summary
Port Status
21 TLS Error
22 Connection Refused
25 TLS Error
53 Connection Refused
80 Large Record Received
443 Certificate error

40. Summary
Port Status
21 TLS Error
22 Connection
Refused
25 TLS Error
53 Connection
Refused
80 Large
Record
Received
443 Certificate
error

41. Port Status
21 TLS Error
22 Connection
Refused
25 TLS Error
53 Connection
Refused
80 Large
Record
Received
443 Certificate
error

42. 42
Thank you
 tamaghna.basu@gmail.com
 twitter.com/titanlambda
 linkedin.com/in/tamaghnabasu