Re: Potential vuln in example for "F.25.1.1. digest()" - Mailing list pgsql-docs

From David G. Johnston
Subject Re: Potential vuln in example for "F.25.1.1. digest()"
Date
Msg-id CAKFQuwZVWK8J3Nw+f=ERH_2hG6iFTVkOc0ciDX1a8vnAb11+HQ@mail.gmail.com
Whole thread Raw
In response to Potential vuln in example for "F.25.1.1. digest()"  (PG Doc comments form <noreply@postgresql.org>)
Responses Re: Potential vuln in example for "F.25.1.1. digest()"
List pgsql-docs
On Tuesday, August 17, 2021, PG Doc comments form <noreply@postgresql.org> wrote:
The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/13/pgcrypto.html
Description:

Hi,
in "F.25.1.1. digest()" you suggest:

CREATE OR REPLACE FUNCTION sha1(bytea) returns text AS $$
    SELECT encode(digest($1, 'sha1'), 'hex')
$$ LANGUAGE SQL STRICT IMMUTABLE;

While this is a great example, it may expose a database app to
vulnerabilities if the attacker succeeds in overriding the function
sha1(...) in the app's user context (schema)


You should read this:


David J.

pgsql-docs by date:

Previous
From: PG Doc comments form
Date:
Subject: Potential vuln in example for "F.25.1.1. digest()"
Next
From: Tom Lane
Date:
Subject: Re: Potential vuln in example for "F.25.1.1. digest()"