Vulnerability Scanner For Websites.: Click To Edit Master Title Style
Vulnerability Scanner For Websites.: Click To Edit Master Title Style
Vulnerability Scanner For Websites.: Click To Edit Master Title Style
Vulnerability
Scanner
for websites.
1
Click to edit Master title style
Browser Security
Mitigating Browser attacks by using proper configuration settings.
2 2
Click to edit Master title style
3 3
Click to listed
OWASP edit Master title
Top 10 style
vulnerabilities
● Injection
● Broken Authentication and session management
● Sensitive data exposure
● XML external entities
● Broken access
● Security Misconfig
● Cross Site Scripting(XSS)
● Insecure Deserialization
● Using known vulnerable components
● Insufficient Logging and monitoring
4 4
Click to edit Master title style
Concept
Same
●
Origin Policy
Eg: Same
Under the origin
policy,: ahttp://example.com
web browser permits
& http://exaple.com/setting
scripts contained in a first web page to access data in a second web
page, but only if both web pages have the same origin.
• Different origin : https://example.com:4657 & http://example.com:8080/settings have different origin
● An origin is defined as a combination of URI scheme, host name and port number.
● This policy prevents a malicious script on one page from obtaining access to sensitive data on another
webpage through the page’s DOM.
5 5
Click to edit Master title style
Prevention:
Set the configuration in your browser such that it follows strict origin
policy with no exception.
Example:
6
Click to edit Master title style
Operation:
● Attacker injects specially crafted code into any legitimate or trusted website.
● User tries to access this so called trusted website.
● Attacker added code runs on user’s(client) machine with full privilege.
Consequence:
● Sensitive data leakage
● Malicious javascript execution
● Key logging
● Cookie theft
● Phishing
● Privilege escalation 7 7
Click to edit Master title style
2) Cross Site request forgery
Operation:
● Attacker is interested in hacking into a Website(web Application) X.
● User(victim) logs into the website X.
● Attacker forces User’s browser to send HTTP request to website X.
● Attacker accesses functionality of the website X using the communication
between the website X and user(already authenticated to website X)
Consequence:
● Sensitive data leakage
● Malicious Javascript execution
● Key logging
Web Server thinks user is attacking the website and is the attacker but actual attacker is sitting
somewhere else, user is victim here.
8 8
Click to edit Master title style
3) Phishing:
Operation:
● Attacker creates a fake website identical to original website.
● Sends it to user asking credentials and send login failed message after
submit. Users generally consider it there typing error and ignore it.
Consequence:
● Sensitive Data leakage
9 9
Click to edit Master title style
4) Insecure data transfer
Operation:
● User transmits data to the web server in plaintext.
● Attacker sniffs and read the data.
● Attacker hijacks user’s web session using the sniffed data.
Consequence:
● Sensitive data leakage
● SSL/TLS based attacks - BEAST(2011), CRIME(2012), LUCKY13(2013),
TIME(2013), BREACH(2013), POODLE(2014), FREAK(2015),
Logjam(2015), SLOTH(2015)
● MiTB attack (Man in The Browser)
1010
Click to edit Master title style
5) WebGL based attack
Operation:
● WebGL is a rendering engine that allows 3D images & animations.
● Most of the graphics card & drives are designed with less emphasis
on security.
● This leads to remote attacker executing arbitrary code using WebGL content
and exploit user’s machine.
Consequence:
● Sensitive data leakage
● Privilege Escalation
1111
Click to edit Master title style
Case Study
Case Study: Firefox web browser security settings - meaning, implications
SSL/TLS security.tls.version.m ax 4 4
1414