> The next topic of discussion is: How does one identify and
> and effectively test for infrastructure dependencies and
> related vulnerabilities in a web application? For instance,
> many web applications rely on underlying infrastructure or
> services external to the application that may or may not
> implement a appropriate level of security. In some cases
> these dependencies (OS specific, Web Proxy specific, DNS
> specific, 3rd party content specific, etc.) are a necessary
> evil of designing a web application, however improper
> implementation or design choices may allow an attacker to
> circumvent webapp security controls altogether by exploiting
> the surrounding infrastructure or 3rd party services. What
> sort of white and black box techniques can one use for
> searching out these weaknesses? What are some common
> mistakes and holes to look for regarding the configuration
> of the surrounding infrastructure or 3rd party services
> (ad banners, streaming media, etc.)?
>
> Please share your experience, points of view, and thoughts on
> this issue.

Great thing to be added.

Its such a broad catagory though. I guess its an issue of trust of the third party application.

1. Does ths input you gather be used in someway to execute commands?
2. Does this input you gather get entered into a DB?
3. Does this input get seen by the public? (like via a website) (Do you filter it in any way or need to?)
4. What are some ways of doing sanity checks of this data.

Just some random thoughts.

- zenocgisecurity.com

>
> -dave
>

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]