HttpOnly

Browsers Supporting HTTPOnly

Using WebGoat's HTTPOnly lesson, the following web browsers have been tested for HTTPOnly capabilities. The results are listed below in table 1.

Table 1: Browsers Supporting HTTPOnly

Browser	Version	Supports HTTPOnly?
Microsoft Internet Explorer	6 (SP1) - 7	Partially*
Mozilla Firefox	2.0.0.5	Partially*
Netscape Navigator	9.0b2	No
Opera	9.22	No

• An attacker could still access the session identifier cookie using a XmlHttpRequest.

Using WebGoat to Test for HTTPOnly Capabilities

Getting Started

Figure 1 - Accessing WebGoat's HTTPOnly Test Lesson

Assuming you have already installed and launched WebGoat, begin by navigating to the ‘HTTPOnly Test’ lesson located within the Cross-Site Scripting (XSS) category. After selecting the ‘HTTPOnly Test’ link, as shown in figure 1, you are now able to begin testing web browsers that support HTTPOnly.

Lesson Goal

If the HTTPOnly flag is set, then your browser should not allow client-side script to access the cookie. Unfortunately, since the attribute is relatively new, several browsers neglect to handle the new attribute properly.

The purpose of this lesson is to test whether your browser supports the HTTPOnly cookie flag. Note the value of the unique2u cookie. If your browser supports HTTPOnly and you enable it for a cookie, client side code should NOT be able to read OR write to that cookie, but the browser can still send its value to the server. However, some browsers only prevent client side read access, but do not prevent write access.

Testing Web Browsers for HTTPOnly Support

The following test was performed on two browsers, Internet Explorer 7 and Opera 9.22, to demonstrate the results when the HTTPOnly flag is enforced properly. As you will see, IE7 properly enforces the HTTPOnly flag, whereas Opera does not properly enforce the HTTPOnly flag.

1) Select the option to turn HTTPOnly off as shown below in figure 2.

Figure 2 - Disabling HTTPOnly

2) After turning HTTPOnly off, select the “Read Cookie” button. 

• An alert dialog box will display on the screen notifying you that since HTTPOnly was not enabled, the ‘unique2u’ cookie was successfully read as shown below in figure 3.

Figure 3 - Cookie Successfully Read with HTTPOnly Off

3) With HTTPOnly remaining disabled, select the “Write Cookie”  button.

• An alert dialog box will display on the screen notifying you that since HTTPOnly was not enabled, the ‘unique2u’ cookie was successfully modified on the client side as shown below in figure 4.

Figure 4 - Cookie Successfully Written with HTTPOnly Off

• As you have seen thus far, browsing without HTTPOnly on is a potential threat. Next, we will enable HTTPOnly to demonstrate how this flag protects the cookie.

4) Select the radio button to enable HTTPOnly as shown below in figure 5.

Figure 5 - Enabling HTTPOnly

5) After enabling HTTPOnly, select the "Read Cookie" button.

• If the browser enforces the HTTPOnly flag properly, an alert dialog box will display on the screen only containing the session ID, not the contents of the ‘unique2u’ cookie as shown below in figure 6.

Figure 6 - Enforced Cookie Read Protection

• However, if the browser does not enforce the HTTPOnly flag properly, an alert dialog box will display both the ‘unique2u’ cookie and session ID as shown below in figure 7.

Figure 7 - Unenforced Cookie Read Protection

• Finally, we will test if the browser allows write access to the cookie with HTTPOnly enabled.

6) Select the "Write Cookie" button.

• If the browser enforces the HTTPOnly flag properly, client side modification will be unsuccessful in writing to the ‘unique2u’ cookie and an alert dialog box will display only containing the session ID as shown below in figure 8.

• However, if the browser does not enforce the write protection property of HTTPOnly flag for the ‘unique2u’ cookie, the cookie will be successfully modified to HACKED on the client side as shown below in figure 9.