19.09.2017 Views

the-web-application-hackers-handbook

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

552 Chapter 13 n Attacking Users: O<strong>the</strong>r Techniques<br />

TRY IT!<br />

http://mdsec.net/auth/249/<br />

Browsing History<br />

Most browsers save a browsing history, which may include any sensitive data<br />

transmitted in URL parameters.<br />

HACK STEPS<br />

1. Identify any instances within <strong>the</strong> <strong>application</strong> in which sensitive data is<br />

being transmitted via a URL parameter.<br />

2. If any cases exist, examine <strong>the</strong> browser history to verify that this data has<br />

been stored <strong>the</strong>re.<br />

TRY IT!<br />

http://mdsec.net/auth/90/<br />

Autocomplete<br />

Many browsers implement a user-configurable autocomplete function for textbased<br />

input fields, which may store sensitive data such as credit card numbers,<br />

usernames, and passwords. Internet Explorer stores autocomplete data in <strong>the</strong><br />

registry, and Firefox stores it on <strong>the</strong> file system.<br />

As already described, in addition to being accessible by local attackers, data in<br />

<strong>the</strong> autocomplete cache can be retrieved via an XSS attack in certain circumstances.<br />

HACK STEPS<br />

1. Review <strong>the</strong> HTML source code for any forms that contain text fields in<br />

which sensitive data is captured.<br />

2. If <strong>the</strong> attribute autocomplete=off is not set, within ei<strong>the</strong>r <strong>the</strong> form<br />

tag or <strong>the</strong> tag for <strong>the</strong> individual input field, data entered is stored within<br />

browsers where autocomplete is enabled.<br />

TRY IT!<br />

http://mdsec.net/auth/260/

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!