oauth: Limit JSON parsing depth in the client
authorJacob Champion <jchampion@postgresql.org>
Fri, 23 May 2025 20:05:33 +0000 (13:05 -0700)
committerJacob Champion <jchampion@postgresql.org>
Fri, 23 May 2025 20:05:33 +0000 (13:05 -0700)
commitcbc8fd0c9aec01f451af5e4eeb0eb2c5d5e47eb2
tree643d5d4f0f6c129b81b0647f4531251cd95e66a7
parent1ca583f6c0f9c178dd2721886c723791ced65520
oauth: Limit JSON parsing depth in the client

Check the ctx->nested level as we go, to prevent a server from running
the client out of stack space.

The limit we choose when communicating with authorization servers can't
be overly strict, since those servers will continue to add extensions in
their JSON documents which we need to correctly ignore. For the SASL
communication, we can be more conservative, since there are no defined
extensions (and the peer is probably more Postgres code).

Reviewed-by: Aleksander Alekseev <aleksander@timescale.com>
Discussion: https://postgr.es/m/CAOYmi%2Bm71aRUEi0oQE9ciBnBS8xVtMn3CifaPu2kmJzUfhOZgA%40mail.gmail.com
src/interfaces/libpq-oauth/oauth-curl.c
src/interfaces/libpq/fe-auth-oauth.c
src/test/modules/oauth_validator/t/001_server.pl
src/test/modules/oauth_validator/t/oauth_server.py