Essential PHP Security and over 2 million other books are available for Amazon Kindle . Learn more

Buy New

or
Sign in to turn on 1-Click ordering.
Buy Used
Used - Like New See details
Price: 4.58

or
 
   
Trade in Yours
For a 1.21 Gift Card
Trade in
More Buying Choices
Have one to sell? Sell yours here
Start reading Essential PHP Security on your Kindle in under a minute.

Don't have a Kindle? Get your Kindle here, or download a FREE Kindle Reading App.

Essential PHP Security [Paperback]

Chris Shiflett
4.2 out of 5 stars  See all reviews (12 customer reviews)
Price: 22.99 & FREE Delivery in the UK. Details
o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
Only 6 left in stock (more on the way).
Dispatched from and sold by Amazon. Gift-wrap available.
Want it tomorrow, 12 July? Choose Express delivery at checkout. Details
‹  Return to Product Overview

Product Description

Review

You've heard the nasty stories about PHP sites being wiped off the web by evil hackers? Sadly it's not scare-mongering as it does happen, and as much as we love PHP it needs proper security to keep your site safe from harm. Plenty of PHP books have the odd chapter on security but at last O'Reilly have published a whole volume dedicated to the cause, with all the code you'll need to keep everything in order. Each chapter covers a different aspect of the application, from form processing to database programming and session management. Written in a straight forward style, it's ideal for every PHP user, but at GBP20 you might expect a little more than just 100 pages." .NET, November 2005 "If you write PHP scripts, get a copy" - Alain Williams, news@UK, March 2006

Book Description

A Guide to Building Secure Web Applications

From the Publisher

The PHP scripting language works beautifully with other open source tools, such as the MySQL database and Apache web server software, to build interactive web applications. But security is still an issue that developers need to address, given the frequency of attacks on web sites. Essential PHP Security explains the types of attacks that hackers use on web sites and how to correctly configure Apache and PHP to guard against them. The author of Essential PHP Security, Chris Shiflett, is an internationally recognized expert in the field of PHP security and this book shows developers how to guard against attacks by writing secure PHP code.

About the Author

Chris Shiflett, an internationally recognized expert in the field of PHP security, is the founder and President of Brain Bulb, a PHP consultancy. Chris has been developing web applications with PHP for several years and regularly speaks at OSCON, ApacheCon, and PHP users conferences in North America. He is the author of the HTTP Developer's Handbook (Sams) and writes frequently about web application security. As an open source advocate, he maintains several open source projects and is a member of the PHP development team.

Excerpt. © Reprinted by permission. All rights reserved.

Chapter 4 Sessions and Cookies

This chapter discusses sessions and the inherent risks associated with stateful web applications. You will first learn the fundamentals of state,cookies,and sessions; then I will discuss several concerns —cookie theft,exposed session data,session fixation, and session hijacking —along with practices that you can employ to help prevent them.

The rumors are true:HTTP is a stateless protocol.This description recognizes the lack of association between any two HTTP requests.Because the protocol does not provide any method that the client can use to identify itself, the server cannot distinguish between clients.

While the stateless nature of HTTP has some important benefits —after all, maintaining state requires some overhead —it presents a unique challenge to developers who need to create stateful web applications. With no way to identify the client, it is impossible to determine whether the user is already logged in, has items in a shop ping cart,or needs to register.

An elegant solution to this problem, originally conceived by Netscape, is a state management mechanism called cookies. Cookies are an extension of the HTTP protocol. More precisely, they consist of two HTTP headers:the Set-Cookie response header and the Cookie request header.

When a client sends a request for a particular URL,the server can opt to include a Set-Cookie header in the response. This is a request for the client to include a corresponding Cookie header in its future requests. Figure 4-1 illustrates this basic exchange.

If you use this concept to allow a unique identifier to be included in each request (in a Cookie header),you can begin to uniquely identify clients and associate their requests together. This is all that is required for state, and this is the primary use of the mechanism.The concept of session management builds upon the ability to maintain state by maintaining data associated with each unique client.This data is kept in a session data store,and it is updated on each request.Because the unique identifier specifies aparticular record in the session data store,it ’s most often called the session identifier.

If you use PHP ’s native session mechanism,all of this complexity is handled for you. When you call session_start(),PHP first determines whether a session identifier is included in the current request.If one is,the session data for that particular session is read and provided to you in the $_SESSION superglobal array.If one is not, PHP generates a session identifier and creates a new record in the session data store. It also handles propagating the session identifier and updating the session data store on
each request.Figure 4-2 illustrates this process.

While this convenience is helpful,it is important to realize that it is not a complete solution. There is no inherent security in PHP ’s session mechanism, aside from the fact that the session identifier it generates is sufficiently random, thereby eliminating the practicality of prediction. You must provide your own safeguards to protect against all other session attacks. I will show you a few problems and solutions in this chapter.

Cookie Theft

One risk associated with the use of cookies is that a user ’s cookies can be stolen by an attacker. If the session identifier is kept in a cookie, cookie disclosure is a serious risk, because it can lead to session hijacking.

The two most common causes of cookie disclosure are browser vulnerabilities and cross-site scripting (discussed in Chapter 2).While no such browser vulnerabilities are known at this time, there have been a few in the past —the most notable ones are in Internet Explorer Versions 4.0,5.0,5.5,and 6.0 (corrective patches are available for each of these vulnerabilities).

While browser vulnerabilities are certainly not the fault of web developers, you may be able to take steps to mitigate the risk to your users. In some cases,you may beable to implement safeguards that practically eliminate the risk.At the very least, you can try to educate your users and direct them to a patch to fix the vulnerability.

‹  Return to Product Overview