Via the so called Invoker Servlet feature, HTTP clients able to invoke arbitrary servlets even if not defined in the web.xml file of the application. Each web application gets a default servlet mapping “/servlet/*” which is mapped to Invoker Servlet provided by the web container. This servlet may load an arbitrary servlet by servlet name or servlet class. As a result, all requests in the following pattern: “/<context-root>/servlet/<servlet-name-or-class>” lead to invocation of the servlet <servlet-name-or-class>. Via this feature, application servlets may be invoked by end users although the application is not willing to provide them (security attacs). For example if a web application contains a buggy servlet but hasn’t declared it into its web.xml file (because it is buggy!), the clients are still able to invoke it. In addition by default there is no authentication needed in order to invoke these servlets. The Invoker Servlet will be disabled by NetWeaver.
Available fix and Supported packages
- ISM-AMC-WB | 2.0 | 2.0
- ISM-AMC-WB | 3.0 | 3.0
- ISM-AMC-WE | 3.0 | 3.0
Advertising Management Classified
Detailed vulnerability information added to RedRays Security Platform. Contact [email protected] for details.