On 11/21/24 19:57, Subhash Udata wrote:
> Hi Adrian,
>
> Thank you for your response regarding the affected versions of
> PostgreSQL. I have a follow-up question for clarification:
>
> The PostgreSQL documentation mentions that the versions with a fix for
> CVE-2024-10979 are *17.1, 16.5, 15.9, 14.14, 13.17, and 12.21*. However,
> your reply states that any version greater than 13+ should suffice.
Any major version 13+. Postgres uses a X.x numbering scheme where X is
major version and x is minor version. If you go here:
https://www.postgresql.org/support/versioning/
you will see that translates to in terms of support. If you move to 13.x
you will have one more year before you would need to move to a newer
version. It is up to you to decide if that is okay or whether you want
to move a version that is newer to have more time to plan the next move.
In either case you should use the latest minor release that is current
at the time. Minor releases are bug/security fixes and it is important
that you keep up with them. The latest round of minor releases where
done yesterday and that is what you should be installing.
>
> Could you please confirm if upgrading to one of the specific versions
> listed above is mandatory, or is it acceptable to upgrade to any version
> higher than 13?
>
> Your guidance will help us determine the appropriate upgrade path for
> our environment.
>
> Thank you for your time and assistance.
>
>
> On Thu, 21 Nov 2024 at 12:24, Adrian Klaver <adrian.klaver@aklaver.com
> <mailto:adrian.klaver@aklaver.com>> wrote:
>
> On 11/20/24 22:44, 김주연 wrote:
> > Hello, I am currently using PostgreSQL 11.10 and would like to
> know if
> > the CVE-2024-10979 vulnerability affects this version.
>
> Postgres 11 is past EOL, see:
>
> https://www.postgresql.org/support/versioning/
> <https://www.postgresql.org/support/versioning/>
>
>
> > If it does impact my version, I would like to know which version I
> > should upgrade to.
>
> Any version from 13+.
>
> --
> Adrian Klaver
> adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
>
>
>
--
Adrian Klaver
adrian.klaver@aklaver.com
