Hello and welcome to our community! Is this your first visit?
Register
Enjoy an ad free experience by logging in. Not a member yet? Register.
Results 1 to 4 of 4
  1. #1
    New to the CF scene
    Join Date
    Jan 2014
    Posts
    2
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Testing Common Website Vulerabilities

    So, one kind of vulnerability that a website might be susceptible to could be tested by doing the following:

    1. Log in as User A
    2. Navigate to a page & copy the URL from the address bar
    3. Logout
    4. Log in as User B
    5. Paste the URL into the address bar and see information for User A

    (p.s. what is the official name for something like this?)

    What I am wondering if there is a good blog post or website out there that would cover this kind and other kinds of vulnerabilities, explaining how they can be tested.

    Thank you.

  • #2
    Master Coder felgall's Avatar
    Join Date
    Sep 2005
    Location
    Sydney, Australia
    Posts
    6,634
    Thanks
    0
    Thanked 649 Times in 639 Posts
    Quote Originally Posted by ericg417 View Post
    So, one kind of vulnerability that a website might be susceptible to could be tested by doing the following:

    1. Log in as User A
    2. Navigate to a page & copy the URL from the address bar
    3. Logout
    4. Log in as User B
    5. Paste the URL into the address bar and see information for User A

    (p.s. what is the official name for something like this?)

    What I am wondering if there is a good blog post or website out there that would cover this kind and other kinds of vulnerabilities, explaining how they can be tested.

    Thank you.
    I cwouldn't have thought that would be a vulnerability. Either the URL for user B to view their own information is the same as the one user A uses to view theirs - in which case pasting like that would display user B's info and not user A OR the URL is only valud for user A and so user B gets redirected.

    I cannot see that anyone would build a system with the vulnerability you describe.

    I would expect the official name for something like that would be "stupid design" as the only way I can see that it would happen is if it were deliberately built into the design.
    Stephen
    Learn Modern JavaScript - http://javascriptexample.net/
    Helping others to solve their computer problem at http://www.felgall.com/

    Don't forget to start your JavaScript code with "use strict"; which makes it easier to find errors in your code.

  • Users who have thanked felgall for this post:

    Arbitrator (01-17-2014)

  • #3
    The fat guy next door VIPStephan's Avatar
    Join Date
    Jan 2006
    Location
    Halle (Saale), Germany
    Posts
    8,642
    Thanks
    6
    Thanked 1,005 Times in 978 Posts
    To me that sounds like a PHP session ID thing without cookies. But I agree that it would be bad design in the first place because that can only come from a programmer doing it wrong, it’s not a natural vulnerability.

  • #4
    New to the CF scene
    Join Date
    Jan 2014
    Posts
    2
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Quote Originally Posted by ericg417 View Post
    What I am wondering if there is a good blog post or website out there that would cover this kind and other kinds of vulnerabilities, explaining how they can be tested.
    In case anyone is interested, one group I have learned about related to this is the Open Web Application Security Project (OWASP).

    They have what appears to be a very good testing guide as part of their OWASP Testing Project page.

    If anyone else is familiar with similar guides or sites, I would be interested.

    Thank you.


  •  

    Tags for this Thread

    Posting Permissions

    • You may not post new threads
    • You may not post replies
    • You may not post attachments
    • You may not edit your posts
    •