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 1ktuDv-0006UO-PK for pgsql-bugs@arkaria.postgresql.org; Mon, 28 Dec 2020 15:14:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ktuDu-0000VW-K7 for pgsql-bugs@arkaria.postgresql.org; Mon, 28 Dec 2020 15:14:14 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ktuDu-0000VP-EG for pgsql-bugs@lists.postgresql.org; Mon, 28 Dec 2020 15:14:14 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ktuDs-00066l-EX for pgsql-bugs@lists.postgresql.org; Mon, 28 Dec 2020 15:14:14 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 0BSFEAuh1598377; Mon, 28 Dec 2020 10:14:10 -0500 From: Tom Lane To: srinivasg@jfrog.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16793: Libxml2 contains a null pointer dereference flaw in xpath.c In-reply-to: <16793-ad84dd312fb888f4@postgresql.org> References: <16793-ad84dd312fb888f4@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Mon, 28 Dec 2020 06:41:47 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1598375.1609168450.1@sss.pgh.pa.us> Date: Mon, 28 Dec 2020 10:14:10 -0500 Message-ID: <1598376.1609168450@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk PG Bug reporting form writes: > Libxml2 contains a null pointer dereference flaw in xpath.c that is > triggered when handling errors for xpointer expressions. this may allow a > context-dependent attacker to crash a process linked against the library. Why are you reporting this here, and not to the libxml2 authors? There's nothing we can do about it. regards, tom lane