> Alternatively, it could be related to:
> https://www.sqlite.org/src/info/4feb3159c6bc3f7e33959
>
> This was released as a part of 3.27.2 and looks like it has the right
> text as well. What concerns me is that the ticket[0] is almost a week
> before TALOS's timeline for "Vendor patched" plus
On Thu, 16 May 2019 20:09:52 +0200
=?UTF-8?B?TMOhc3psw7MgQsO2c3rDtnJtw6lueWkgKEdDUyk=?= wrote:
> Hi,
>
> On Thu, May 16, 2019 at 11:57 AM Pirate Praveen
> wrote:
> > On Fri, 10 May 2019 21:04:33 +0200 Salvatore Bonaccorso
> > wrote:
> > > Source: sqlite3
> > > The following vulnerability was
Hi,
On Thu, May 16, 2019 at 11:57 AM Pirate Praveen
wrote:
> On Fri, 10 May 2019 21:04:33 +0200 Salvatore Bonaccorso
> wrote:
> > Source: sqlite3
> > The following vulnerability was published for sqlite3.
> > CVE-2019-5018[0]:
> > Window Function Remote Code Execution Vulnerability
> Could this
On Fri, 10 May 2019 21:04:33 +0200 Salvatore Bonaccorso
wrote:
> Source: sqlite3
> Version: 3.27.2-2
> Severity: grave
> Tags: security
> Justification: user security hole
>
> Hi,
>
> The following vulnerability was published for sqlite3.
>
> CVE-2019-5018[0]:
> Window Function Remote Code
Source: sqlite3
Version: 3.27.2-2
Severity: grave
Tags: security
Justification: user security hole
Hi,
The following vulnerability was published for sqlite3.
CVE-2019-5018[0]:
Window Function Remote Code Execution Vulnerability
The issue must have been fixed upstream around 2019-03-28, but no
5 matches
Mail list logo
