Re: [Mod-security-developers] 2.9.0-RC1 test results

[Walter H. <mo...@sp...>]

An update about this crash. Last week, I got very similar repeated segfaults on three boxes running ModSecurity 2.7.7! Of course I don’t have debug builds running everywhere, but it seemed to be in the same function.

Interestingly, more out of luck than anything else, two of these boxes were slated for upgrading to FreeBSD 10.1, and I noticed the segfaults completely went away on them for a week (knock on wood) while I was having them almost daily.

So I am now thinking this is *not* a regression in 2.9.0.

My working theory now is, either the interaction of some library update (pcre? libxml2?) with the FreeBSD 10.0 (clang?) runtime leads to memory corruption.


> 2) High prio: Undiagnosed persistent crash. https://gist.github.com/lifeforms/4356643edfe8f39c2991 <https://gist.github.com/lifeforms/4356643edfe8f39c2991>
> 
> Got the same crash on a second test box today.
> I have updated the gist with information from a debug build: https://gist.github.com/lifeforms/4356643edfe8f39c2991 <https://gist.github.com/lifeforms/4356643edfe8f39c2991>
> 
> This crash appears to be serious. I don’t think I’ve ever seen ModSecurity segfault while parsing a request before. Since it starts happening on a random moment of the day, I’m a bit concerned this might be a remote DoS vuln, so I’m reverting to 2.7.7 on the public boxes.
> 
> I have kept some core files, but it’s been a long time since I worked with gdb so let me know if I should extract more info out of them.
> 
> Is there a way to enable asserts in the code so we can find out why/when node is unset?


-- 
Walter Hop | PGP key: https://lifeforms.nl/pgp