From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: 1157401338@qq.com
Subject: BUG #17622: a potential bug of NPD
Date: Mon, 26 Sep 2022 03:00:41 +0000
Message-ID: <17622-1163f4b81b882c9d@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 17622
Logged by: a potential bug of NPD
Email address: 1157401338@qq.com
PostgreSQL version: 14.5
Operating system: ubuntu20.04
Description:
Hi, I found a potential null pointer dereference bug in the project source
code of postgre, and I have shown the execution sequence of the program that
may generate the bug on a graph,which can be access by
https://user-images.githubusercontent.com/87304478/192184761-d7713433-074a-4178-bdc2-78f2bf4fb764.pn....
The red text illustrates the steps that generate the bug, the red arrows
represent the control flow,the file path can be seen in the blue framed
section.
It should be noted that in the call to the timestamp_to_asc function, in
addition to the fact that step3 returns null, it may also return null
because of BAD_TIMESTAMP, as shown in line 287 of timestamp.c, after errno
is set to the corresponding value, return null to caller.
Although the code shown is for version 12.12 but is still exist in current
version
would you can help to check if this bug is true?thank you for your effort
and patience!
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, 1157401338@qq.com
Subject: Re: BUG #17622: a potential bug of NPD
In-Reply-To: <17622-1163f4b81b882c9d@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox