Re: [PATCH] Fix buffer not null terminated on (ecpg lib) - Mailing list pgsql-hackers

From Andres Freund
Subject Re: [PATCH] Fix buffer not null terminated on (ecpg lib)
Date
Msg-id 20210615184819.jcpastnzafp2xxge@alap3.anarazel.de
Whole thread Raw
In response to Re: [PATCH] Fix buffer not null terminated on (ecpg lib)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCH] Fix buffer not null terminated on (ecpg lib)  (Ranier Vilela <ranier.vf@gmail.com>)
List pgsql-hackers
Hi,

On 2021-06-15 13:53:08 -0400, Tom Lane wrote:
> Andres Freund <andres@anarazel.de> writes:
> > On 2021-06-15 07:40:46 -0300, Ranier Vilela wrote:
> >> memcpy would not suffer from it?
> 
> > It'd not be correct for short sqlstates - you'd read beyond the end of
> > the source buffer. There are cases of it in the ecpg code.
> 
> What's a "short SQLSTATE"?  They're all five characters by definition.

I thought there were places that just dealt with "00" etc. And there are - but
it's just comparisons.

I still don't fully feel comfortable just using memcpy() though, given that
the sqlstates originate remotely / from libpq, making it hard to rely on the
fact that the buffer "ought to" always be at least 5 bytes long? As far as I
can tell there's no enforcement of PQresultErrorField(..., PG_DIAG_SQLSTATE)
being that long.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: unnesting multirange data types
Next
From: Andres Freund
Date:
Subject: Re: Improving the isolationtester: fewer failures, less delay