the-web-application-hackers-handbook

Chapter 21 n A Web Application Hacker’s Methodology 845
10 Test for Shared Hosting Vulnerabilities
10.1. Test segregation in shared infrastructures
10.2. Test segregation between ASP-hosted applications
Figure 21-11: Testing for shared hosting vulnerabilities
10.1 Test Segregation in Shared Infrastructures
10.1.1 If the application is hosted in a shared infrastructure, examine the access
mechanisms provided for customers of the shared environment to update
and manage their content and functionality. Consider the following
questions:
n Does the remote access facility use a secure protocol and suitably
hardened infrastructure?
n Can customers access files, data, and other resources that they do not
legitimately need to access?
n Can customers gain an interactive shell within the hosting environment
and execute arbitrary commands?
10.1.2 If a proprietary application is used to allow customers to configure and
customize a shared environment, consider targeting this application as
a way to compromise the environment itself and individual applications
running within it.
10.1.3 If you can achieve command execution, SQL injection, or arbitrary file
access within one application, investigate carefully whether this provides
any way to escalate your attack to target other applications.
10.2 Test Segregation Between ASP-Hosted Applications
10.2.1 If the application belongs to an ASP-hosted service composed of a
mix of shared and customized components, identify any shared components
such as logging mechanisms, administrative functions, and
database code components. Attempt to leverage these to compromise
the shared portion of the application and thereby attack other individual
applications.