mirror of
https://github.com/mauriceboe/TREK.git
synced 2026-11-20 02:56:10 +00:00
f19aae6821
The guard ended a -- comment at LF only, while Postgres ends it at CR as well, so "select 1 --\rfrom public.users" hid a qualified name from the guard that Postgres then read, and with no args a second statement after the CR ran as TREK's role. It also only looked for INTO at the top level of a SELECT, so "(select ... into temp users)" made a temporary table that shadowed TREK's own users table on the pooled connection. The tokenizer now skips exactly what Postgres skips as whitespace, ends a line comment at CR or LF, and refuses any character the two read differently (other control characters, non-ASCII whitespace such as U+00A0, U+FEFF and U+2028, and the non-decimal and underscored numbers Postgres before 16 reads another way) instead of guessing. INTO is refused anywhere but after INSERT or MERGE, at any depth, and the words TEMP and TEMPORARY anywhere outside a string or quoted name. The guard tests carry both payloads and their variants; the Postgres lane runs them against the real database, proves a second statement in one text is refused by Postgres over the extended protocol, and that a temporary table never shadows TREK's or a plugin's tables.