[Bug 62068] New: apreq_hook_find_param Invinite loop

[bu...@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=62068

            Bug ID: 62068
           Summary: apreq_hook_find_param Invinite loop
           Product: Apache httpd-2
           Version: 2.2.22
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libapreq2
          Assignee: bugs@httpd.apache.org
          Reporter: mk@vautron.de
  Target Milestone: ---

Created attachment 35713
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=35713&action=edit
GDB Output and sample request

Hi List,

we're having a problem with the libapreq (libapreq2-2.13). Sometimes HTTP
requests are resulting in a segfault of our apache:

[Wed Jan 31 11:51:26 2018] [notice] child pid 7417 exit signal Segmentation
faul
t (11)

We've generated a core dump (please see attached gdboutput) and traced it back
to
the apreq_hook_find_param function. It looks like the hook pointer sometimes
gets 
corrupted and points to itself, resulting in a segfault.

I've also attached the (anonymized) request which results in the segfault.

Please contact me if you need further information.

Thank you and best regards
Martin

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org

[Bug 62068] apreq_hook_find_param Invinite loop

[bu...@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=62068

William A. Rowe Jr. <wr...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |LATER
             Status|NEW                         |RESOLVED
           Keywords|                            |MassUpdate

--- Comment #1 from William A. Rowe Jr. <wr...@apache.org> ---
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.

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org