Groups | Search | Server Info | Keyboard shortcuts | Login | Register
Groups > comp.databases.postgresql > #847
| From | sten.unto@gmail.com (Unto Sten) |
|---|---|
| Newsgroups | comp.databases.postgresql |
| Subject | plpgsql function SQL injection vulnerability? |
| Date | 2018-10-25 17:11 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <pqstfl$bse$1@dont-email.me> (permalink) |
Hello! I have a question that is probably easy for the PostgreSQL experts. Consider a simple function: ################################### CREATE OR REPLACE FUNCTION search_for_address(re TEXT) RETURNS TABLE(line VARCHAR) AS $$ BEGIN RETURN QUERY SELECT k.line FROM kdata k WHERE k.line ~* re ORDER BY k.line ASC LIMIT 100; END; $$ LANGUAGE plpgsql SECURITY DEFINER; ################################### Is this function vulnerable to SQL injection attacks via input 're TEXT' or does the PG parser prevent it in these plpgsql functions? To be safe, I do input validation before calling search_for_address(re TEXT) but I would like to know the truth here. If the function is vulnerable, could you please provide an exact string to prove it? Thanks. I have tried to attack it, but my attempts failed. Best regards, Unto Sten
Back to comp.databases.postgresql | Previous | Next — Next in thread | Find similar
plpgsql function SQL injection vulnerability? sten.unto@gmail.com (Unto Sten) - 2018-10-25 17:11 +0000
Re: plpgsql function SQL injection vulnerability? George Neuner <gneuner2@comcast.net> - 2018-10-26 00:47 -0400
Re: plpgsql function SQL injection vulnerability? Laurenz Albe <laurenz@nospam.pn> - 2018-10-26 12:47 +0000
Re: plpgsql function SQL injection vulnerability? sten.unto@gmail.com (Unto Sten) - 2018-10-26 19:06 +0000
Re: plpgsql function SQL injection vulnerability? sten.unto@gmail.com (Unto Sten) - 2018-10-26 19:08 +0000
csiph-web