Re: [Regression in httpd 2.4.52] mod_dav: Potentially unbounded memory usage in PROPFIND with dav_get_props() and dav_propfind_walker()

On 1/18/22 2:58 PM, Evgeny Kotkov wrote: > Ruediger Pluem writes: > >> Can you please check if the below patch fixes your issue? > > I have to say that the reason and the original intention of using > resource->pool's userdata here are still somewhat unclear to me. An application seems to

Re: [Regression in httpd 2.4.52] mod_dav: Potentially unbounded memory usage in PROPFIND with dav_get_props() and dav_propfind_walker()

Ruediger Pluem writes: > Can you please check if the below patch fixes your issue? I have to say that the reason and the original intention of using resource->pool's userdata here are still somewhat unclear to me. But it does look like the patch performs the allocation only once per

Re: [Regression in httpd 2.4.52] mod_dav: Potentially unbounded memory usage in PROPFIND with dav_get_props() and dav_propfind_walker()

On 1/14/22 1:57 PM, Evgeny Kotkov wrote: > Hi, > > I might have stumbled across a regression in httpd 2.4.52 where mod_dav was > changed in a way where dav_get_props() now allocates data in resource->pool. > > I think that r1879889 [1] is the change that is causing the new behavior. > This

[Regression in httpd 2.4.52] mod_dav: Potentially unbounded memory usage in PROPFIND with dav_get_props() and dav_propfind_walker()

Hi, I might have stumbled across a regression in httpd 2.4.52 where mod_dav was changed in a way where dav_get_props() now allocates data in resource->pool. I think that r1879889 [1] is the change that is causing the new behavior. This change has been backported to 2.4.x in r1895893 [2].