Re: BUG #19491: Segmentation fault triggered by IS NULL

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: ZhangChi <798604270(at)qq(dot)com>
Cc: Srinath Reddy Sadipiralla <srinath2133(at)gmail(dot)com>, Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com>, pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #19491: Segmentation fault triggered by IS NULL
Date: 2026-08-04 09:29:29
Message-ID: anGwARIffUrihqrP@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2026-Aug-04, ZhangChi wrote:

> Thanks all for fixing this issue and making pg better. Since this
> issue can reliably crash the PostgreSQL server, I would like to ask
> whether it should be treated as a security vulnerability and whether
> it is eligible for CVE assignment.

Hello,

Server crashes ("denial of service") requiring an authenticated user are
not, by themselves, considered security vulnerabilities. See "What is a
Security Vulnerability in PostgreSQL?" here:

https://www.postgresql.org/support/security/

Thanks

--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"People get annoyed when you try to debug them." (Larry Wall)

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Álvaro Herrera 2026-08-04 09:48:32 Re: BUG #19607: Bug 18: `pg_surgery` infinite loop in `heap_force_common`
Previous Message Zexin Li 2026-08-04 08:54:03 Re: BUG #19598: pg_waldump: -s/-e accept out-of-range WAL locations and silently use the low 32 bits