| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "sathyendran(dot)vellaisamy(at)intel(dot)com" <sathyendran(dot)vellaisamy(at)intel(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #18702: Critical & High Security vulnerability issue with Trivy Scan in postgres 16 |
| Date: | 2024-11-12 14:21:39 |
| Message-ID: | CAKFQuwa3h-dWmfHtu3YiLfKb14+0Eq7EuEUWG40T9-H0EjS5KA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tuesday, November 12, 2024, PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:
> The following bug has been logged on the website:
>
> Bug reference: 18702
> Logged by: Sathyendran Vellaisamy
> Email address: sathyendran(dot)vellaisamy(at)intel(dot)com
> PostgreSQL version: 16.0
> Operating system: Ubuntu
> Description:
>
>
If you are scanning the unsupported v16.0 instead of a latest supported
release (a new one comes out this week) then you are not doing things
correctly and you need to change your own procedures to ensure you only
test and use supported releases.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2024-11-12 14:56:07 | Re: BUG #18675: Postgres is not realasing memory causing OOM |
| Previous Message | PG Bug reporting form | 2024-11-12 10:12:24 | BUG #18702: Critical & High Security vulnerability issue with Trivy Scan in postgres 16 |