Hi Jonas,
On Wed, Jul 03, 2019 at 02:48:51PM +0200, Jonas Meurer wrote:
> Hi Ola,
>
> thanks for your response!
>
> Ola Lundqvist:
> > I have now looked into this problem to see if I can out something.
> >
> > What I have done is to backtrack whether the code is ever executed by
> > sqlite and
Hi Jonas,
On Wed, Jul 03, 2019 at 02:48:51PM +0200, Jonas Meurer wrote:
> Hi Ola,
>
> thanks for your response!
>
> Ola Lundqvist:
> > I have now looked into this problem to see if I can out something.
> >
> > What I have done is to backtrack whether the code is ever executed by
> > sqlite and
Hi Ola,
thanks for your response!
Ola Lundqvist:
> I have now looked into this problem to see if I can out something.
>
> What I have done is to backtrack whether the code is ever executed by
> sqlite and I cannot find that it can be.
>
> rtreenode function is registered using sqlite3_create_fu
Hi Jonas
I have now looked into this problem to see if I can out something.
What I have done is to backtrack whether the code is ever executed by
sqlite and I cannot find that it can be.
rtreenode function is registered using sqlite3_create_function
in sqlite3_rtree_init. But I cannot find that
(Putting Security Team in the loop as they're very likely to run into
the same problem.)
Hello,
I spent quite some hours trying to backport the fix for CVE-2019-8457[1]
to sqlite3 in Jessie. That ended in backporting huge amounts of upstream
changes and in the end I decided to not further go this
