Re: CVE-2024-10979 Vulnerability Impact on PostgreSQL 11.10

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Subhash Udata <subhashudata(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: 김주연 <mysylph(at)gmail(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: CVE-2024-10979 Vulnerability Impact on PostgreSQL 11.10
Date: 2024-11-22 04:44:07
Message-ID: dde2f686-a268-4564-95e7-70783595e2e7@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 11/21/24 20:31, Subhash Udata wrote:
> Thank you for your detailed response. I would like to clarify my
> situation further to ensure I take the appropriate steps.
>
> Currently, my environment is running *PostgreSQL 15.0*. I understand
> that version *15.9* contains the fix for CVE-2024-10979, as mentioned in
> the release notes.

Whoa, I thought the topic of discussion from your first post and the
email subject was:

"I am currently using PostgreSQL 11.10 and would like to know if the
CVE-2024-10979 vulnerability affects this version."

>
> Given that I am not using the *PL/Perl* extension in my environment, I
> wanted to ask:
>
> * Is it still mandatory to upgrade specifically to version *15.9*, or
> would remaining on version *15.0* suffice in this case?
>
> I appreciate your guidance on whether this upgrade is necessary,
> considering the specifics of my setup.

The upgrades fixed more then this issue, so yes you should upgrade for
all the reasons listed in the release notes for 15.1 to 15.10.

>
> Thank you for your time and support.
>
>
> On Fri, 22 Nov 2024 at 09:39, David G. Johnston
> <david(dot)g(dot)johnston(at)gmail(dot)com <mailto:david(dot)g(dot)johnston(at)gmail(dot)com>> wrote:
>
> On Thursday, November 21, 2024, Subhash Udata
> <subhashudata(at)gmail(dot)com <mailto:subhashudata(at)gmail(dot)com>> wrote:
>
>
> 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.
>
> 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
>
>
> It was literally just reported and fixed.  If you are on a supported
> release of PostgreSQL you have the fix.  If you are not, you don’t.
>
> At this point only major versions 13+ are supported.
>
> Upgrading to an unsupported minor release is never recommended.
>
> The fact you are on version 11 means you should not expect an answer
> to the question whether this newly discovered CVE affects you - that
> would be expecting support for a long-unsupported version.
>
> Which of the 5 currently supported releases you should upgrade to is
> a decision you need to make given your circumstances.
>
> David J.
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David G. Johnston 2024-11-22 04:51:32 Re: CVE-2024-10979 Vulnerability Impact on PostgreSQL 11.10
Previous Message Ron Johnson 2024-11-22 04:39:38 Re: CVE-2024-10979 Vulnerability Impact on PostgreSQL 11.10