11.07.2015 Views

Improving Web Application Security: Threats and - CGISecurity

Improving Web Application Security: Threats and - CGISecurity

Improving Web Application Security: Threats and - CGISecurity

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

64 Part I: Introduction to <strong>Threats</strong> <strong>and</strong> CountermeasuresRatings do not have to use a large scale because this makes it difficult to rate threatsconsistently alongside one another. You can use a simple scheme such as High (1),Medium (2), <strong>and</strong> Low (3).When you clearly define what each value represents for your rating system, it helpsavoids confusion. Table 3.6 shows a typical example of a rating table that can be usedby team members when prioritizing threats.Table 3.6 Thread Rating TableRating High (3) Medium (2) Low (1)D DamagepotentialLeaking sensitiveinformationThe attacker cansubvert the securitysystem; get full trustauthorization; run asadministrator; uploadcontent.Leaking trivialinformationR Reproducibility The attack can bereproduced every time<strong>and</strong> does not require atiming window.E Exploitability A novice programmercould make the attackin a short time.A Affected users All users, defaultconfiguration, keycustomersD Discoverability Published informationexplains the attack. Thevulnerability is found inthe most commonlyused feature <strong>and</strong> isvery noticeable.The attack can bereproduced, but onlywith a timing window<strong>and</strong> a particular racesituation.A skilled programmercould make the attack,then repeat the steps.Some users, nondefaultconfigurationThe vulnerability is in aseldom-used part ofthe product, <strong>and</strong> only afew users should comeacross it. It would takesome thinking to seemalicious use.The attack is verydifficult to reproduce,even with knowledge ofthe security hole.The attack requires anextremely skilledperson <strong>and</strong> in-depthknowledge every timeto exploit.Very small percentageof users, obscurefeature; affectsanonymous usersThe bug is obscure,<strong>and</strong> it is unlikely thatusers will work outdamage potential.After you ask the above questions, count the values (1–3) for a given threat. Theresult can fall in the range of 5–15. Then you can treat threats with overall ratings of12–15 as High risk, 8–11 as Medium risk, <strong>and</strong> 5–7 as Low risk.For example, consider the two threats described earlier:● Attacker obtains authentication credentials by monitoring the network.●SQL comm<strong>and</strong>s injected into application.

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

Saved successfully!

Ooh no, something went wrong!