Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nYD5H-0007mp-70 for pgsql-bugs@arkaria.postgresql.org; Sat, 26 Mar 2022 20:32:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nYD5G-0008BU-22 for pgsql-bugs@arkaria.postgresql.org; Sat, 26 Mar 2022 20:32:26 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nYD5F-0008BK-Q6 for pgsql-bugs@lists.postgresql.org; Sat, 26 Mar 2022 20:32:25 +0000 Received: from smtp.outgoing.loopia.se ([93.188.3.37]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nYD5D-0007zR-46 for pgsql-bugs@lists.postgresql.org; Sat, 26 Mar 2022 20:32:24 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id 919B52F1E1C6 for ; Sat, 26 Mar 2022 21:32:20 +0100 (CET) Received: from s630.loopia.se (unknown [172.22.191.6]) by s807.loopia.se (Postfix) with ESMTP id 831C32E2E209; Sat, 26 Mar 2022 21:32:20 +0100 (CET) Received: from s476.loopia.se (unknown [172.22.191.6]) by s630.loopia.se (Postfix) with ESMTP id 7716713B3B7A; Sat, 26 Mar 2022 21:32:20 +0100 (CET) X-Virus-Scanned: amavisd-new at amavis.loopia.se X-Spam-Flag: NO X-Spam-Score: -1 X-Spam-Level: X-Spam-Status: No, score=-1 tagged_above=-999 required=6.2 tests=[ALL_TRUSTED=-1] autolearn=disabled Received: from s499.loopia.se ([172.22.191.6]) by s476.loopia.se (s476.loopia.se [172.22.190.16]) (amavisd-new, port 10024) with LMTP id fwA8IGMDKhFZ; Sat, 26 Mar 2022 21:32:20 +0100 (CET) X-Loopia-Auth: user X-Loopia-User: daniel@yesql.se X-Loopia-Originating-IP: 89.255.232.193 Received: from [192.168.72.144] (customer-89-255-232-193.stosn.net [89.255.232.193]) (Authenticated sender: daniel@yesql.se) by s499.loopia.se (Postfix) with ESMTPSA id 111AA1CE5D67; Sat, 26 Mar 2022 21:32:20 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\)) Subject: Re: OpenSSL v1.1.1n in postgres From: Daniel Gustafsson In-Reply-To: Date: Sat, 26 Mar 2022 21:32:19 +0100 Cc: "pgsql-bugs@lists.postgresql.org" Content-Transfer-Encoding: quoted-printable Message-Id: <3CF81050-F834-4000-99C0-8BC2E805CFAB@yesql.se> References: To: "Vibhu Chauhan (iDEAS-ER&D)" X-Mailer: Apple Mail (2.3608.120.23.2.7) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 26 Mar 2022, at 18:32, Vibhu Chauhan (iDEAS-ER&D) = wrote: > Hi Postgres support, This is the bug reporting mailing list, and this is not a bug report. = Please use pgsql-general for future questions like these. > In one security scan we found that OpenSSL v1.1.1k is vulnerable which = is sub-component of postgres 13.3. =46rom below link we came to know = that affected OpenSSL version 1.1.1k is fixed in 1.1.1n version. We = wanted to know which postgres version having this fix version of = OpenSSL? And is there any steps to mitigate the risk of version 1.1.1k? PostgreSQL doesn't come statically linked to any OpenSSL version, you = need to ask your system administrators and/or PostgreSQL service provider about = this. -- Daniel Gustafsson https://vmware.com/