Bug 146657

Summary: CAN-2005-0088 mod_python information leak
Product: Red Hat Enterprise Linux 4 Reporter: Josh Bressers <bressers>
Component: mod_pythonAssignee: Joe Orton <jorton>
Status: CLOSED ERRATA QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0CC: mjc, security-response-team
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: impact=moderate,public=20050210
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-02-15 09:04:52 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 142822    

Description Josh Bressers 2005-01-31 15:57:20 UTC 
*** This bug has been split off bug 146655 ***

------- Original comment by Josh Bressers (Security Response Team) on 2005.01.31
10:43 -------

Graham Dumpleton discovered a flaw which can affect anyone using the
publisher handle of the Apache Software Foundation mod_python.  The
publisher handle lets you publish objects inside modules to make them
callable via URL.  The flaw allows a carefully crafted URL to obtain extra
information that should not be visible (information leak).


Gregory (Grisha) Trubetskoy gives this example:

        For example, given a published module foo.py:

        _secret_info = "BLAH"

        def hello(req):

             return "Hello world!"

        A request to http://yourhost/fo.py/hello would result in (as expected)
        "Hello world!". _scret_info is inaccessible by the rules of the 
        publisher because it begins with an underscore.

        Here is the problem. A request to

        http://yourhost/foo.py/hello/func_globals

        Would result in a slew of interesting info (too much to paste in here),
        among them the name and value of _secret_info and other things such as 
        the full pathname of the file foo.py.

        The fix (tennatively) is this patch to the publisher.py file. As a
        super-quick hack perhaps dissalowing access to anything that contains
        "func_" in the apache config may be the way to go.



The patch for this issue is attachment 110440 [details].
Comment 1 Joe Orton 2005-02-02 15:53:03 UTC 
Erratum queued as RHSA-2005:100.
Comment 2 Mark J. Cox 2005-02-10 13:58:35 UTC 
removing embargo
Comment 3 Mark J. Cox 2005-02-15 09:04:52 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2005-100.html