Commentary

George Hulme
 

Web App Threats Rising

Great news: 1 out of 10 Web sites you visit may actually be secure.

Great news: 1 out of 10 Web sites you visit may actually be secure.According to a report published yesterday by Web security firm WhiteHat Security, nine out of 10 Web sites have significant vulnerabilities that can be exploited by attackers. The report also finds that Web sites, on average, have seven flaws that make them vulnerable to attack.

Not surprisingly, cross-site scripting (XSS) vulnerabilities is still the most prevalent Web security problem out there, with 70% of Web sites vulnerable to this form of attack.


More Security Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Simply put, XXS is a vulnerability that allows attackers (or anyone who feels like it, really) to inject code, such as HTML, into a site. These types of vulnerabilities can be used to bypass Web site access controls, and has been used by phishers to conduct mass-scale fraud.

Now, fraudsters are likely to turn to an emerging type of attack, similar to XXS, known as cross-site request forgery, or CSRF. Beyond being yet another acronym we need to remember, this type of attack doesn't require code be injected into a Web site.

Rather, users authenticated, or logged-in, to a Web site can be attacked while the session is active. This means, if you're logged into your bank, it could be possible for someone to use your active session to transfer money out of your account without you being aware. Until it's too late, of course.

Here's what WhiteHat Security had to say about CSRF in a statement:

However, CSRF, while known in the public domain for years, has recently garnered more attention from malicious hackers. Attackers using CSRF can easily force a user's Web browser to send unintended HTTP requests such as fraudulent wire transfers, change passwords and download illegal content. Effective automated CSRF detection techniques have eluded all technology scanning vendors in the space, making identification a largely manual process.

That means it's tough to find this flaw in existing code. Your best defense make be making sure you pick the one site (out of 10) that is secure.

There may be a couple more practical steps you can take to avoid CSRF attacks on your sessions:

  • Don't have multiple Web sites open in your browser while doing any type of banking, or other types of high-value transactions.
  • Always remember to properly log out from credit card and banking-related Web sites.
  • Anyone else have any useful suggestions?


    Related Reading




    Currently we allow the following HTML tags in comments:

    Single tags

    These tags can be used alone and don't need an ending tag.

    <br> Defines a single line break

    <hr> Defines a horizontal line

    Matching tags

    These require an ending tag - e.g. <i>italic text</i>

    <a> Defines an anchor

    <b> Defines bold text

    <big> Defines big text

    <blockquote> Defines a long quotation

    <caption> Defines a table caption

    <cite> Defines a citation

    <code> Defines computer code text

    <em> Defines emphasized text

    <fieldset> Defines a border around elements in a form

    <h1> This is heading 1

    <h2> This is heading 2

    <h3> This is heading 3

    <h4> This is heading 4

    <h5> This is heading 5

    <h6> This is heading 6

    <i> Defines italic text

    <p> Defines a paragraph

    <pre> Defines preformatted text

    <q> Defines a short quotation

    <samp> Defines sample computer code text

    <small> Defines small text

    <span> Defines a section in a document

    <s> Defines strikethrough text

    <strike> Defines strikethrough text

    <strong> Defines strong text

    <sub> Defines subscripted text

    <sup> Defines superscripted text

    <u> Defines underlined text

    InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

    Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
    T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
    Subscribe to RSS

    Resource Links