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.

Chapter 21 n A Web Application Hacker’s Methodology 851<br />

or within HTML metatags), <strong>the</strong> page concerned may be cached by one<br />

or more browsers:<br />

Expires: 0<br />

Cache-control: no-cache<br />

Pragma: no-cache<br />

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

transmitted via a URL parameter. If any cases exist, examine <strong>the</strong> browser<br />

history to verify that this data has been stored <strong>the</strong>re.<br />

12.2.5 For all forms that are used to capture sensitive data from <strong>the</strong> user (such<br />

as credit card details), review <strong>the</strong> form’s HTML source. If <strong>the</strong> attribute<br />

autocomplete=off is not set, within ei<strong>the</strong>r <strong>the</strong> form tag or <strong>the</strong> tag for <strong>the</strong><br />

individual input field, data entered is stored within browsers that support<br />

autocomplete, provided that <strong>the</strong> user has not disabled this feature.<br />

12.2.6 Check for technology-specific local storage.<br />

12.2.6.1 Check for Flash local objects using <strong>the</strong> BetterPrivacy plug-in<br />

for Firefox.<br />

12.2.6.2 Check any Silverlight isolated storage in this directory:<br />

C:\Users\{username}\AppData\LocalLow\Microsoft\<br />

Silverlight\<br />

12.2.6.3 Check any use of HTML5 local storage.<br />

12.3 Check for Weak SSL Ciphers<br />

12.3.1 If <strong>the</strong> <strong>application</strong> uses SSL for any of its communications, use <strong>the</strong> tool<br />

THCSSLCheck to list <strong>the</strong> ciphers and protocols supported.<br />

12.3.2 If any weak or obsolete ciphers and protocols are supported, a suitably<br />

positioned attacker may be able to perform an attack to downgrade or<br />

decipher <strong>the</strong> SSL communications of an <strong>application</strong> user, gaining access<br />

to his sensitive data.<br />

12.3.3 Some <strong>web</strong> servers advertise certain weak ciphers and protocols as supported<br />

but refuse to actually complete a handshake using <strong>the</strong>se if a<br />

client requests <strong>the</strong>m. This can lead to false positives when you use <strong>the</strong><br />

THCSSLCheck tool. You can use <strong>the</strong> Opera browser to attempt to perform<br />

a complete handshake using specified weak protocols to confirm<br />

whe<strong>the</strong>r <strong>the</strong>se can actually be used to access <strong>the</strong> <strong>application</strong>.<br />

12.4 Check Same-Origin Policy Configuration<br />

12.4.1 Check for <strong>the</strong> /crossdomain.xml file. If <strong>the</strong> <strong>application</strong> allows unrestricted<br />

access (by specifying ), Flash objects

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

Saved successfully!

Ooh no, something went wrong!