Bug 35781

Summary: ap_sub_req_method_uri() bypasses Limit security config
Product: Apache httpd-2 Reporter: Dan Kubb <dan.kubb-apache>
Component: CoreAssignee: Apache HTTPD Bugs Mailing List <bugs>
Severity: normal Keywords: MassUpdate
Priority: P2    
Version: 2.1-HEAD   
Target Milestone: ---   
Hardware: All   
OS: All   

Description Dan Kubb 2005-07-18 18:58:54 UTC
When using ap_sub_req_method_uri() to perform a subrequest, it skips over all stages straight to the 
Type Handler phase.  This skips over any access/authentication/authorization handlers that have been 
defined, and allows the type/response phases to be executed directly -- when in fact the client may not 
be permitted by Limit security settings.

In my particular setup, I allow GET/HEAD/POST/OPTIONS to all users; but I limit PUT/DELETE to specific 
users.  I have a piece of code that executes when a POST (that contains specific instructions) is recieved, 
that performs a subrequest on the current URI as a PUT/DELETE.   In effect, I am tunneling PUT/DELETE 
over POST, something that allows me to have a uniform interface for all clients, while still allowing 
normal behaviour for web browser clients that are limited to GET/POST method calls only.

The behaviour I expected was for the security limits I set up for PUT/DELETE to be honored, and 
disallow the request should something in the AAA stages not pass; however the use of 
ap_run_quick_handler() at the end of ap_sub_req_method_uri() bypasses all of these handlers.
Comment 1 William A. Rowe Jr. 2018-11-07 21:08:12 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.