Skip to content

fix: reject SQL escape strings in read-only queries - #635

Merged
Sev7eNup merged 1 commit into
mainfrom
fix/612-sql-escape-string-guard
Oct 24, 2026
Merged

Sev7eNup merged 1 commit into
mainfrom
fix/612-sql-escape-string-guard

Conversation

@Sev7eNup

Copy link
Copy Markdown
Owner

What & why

Reject PostgreSQL E/e escape-string literals at the shared read-only query boundary so protected-column inspection cannot be bypassed.

Cover the reported exploit through DbAdmin and SqlKnowledgeReader, plus ordinary literals, comments and dollar quoting.

Fixes #612

Testing

Api.Tests: FullyQualifiedName~DbAdmin|FullyQualifiedName~SqlKnowledgeReaderTests — 228 passed. The exploit is exercised through both production query entry points, alongside accepted quoting/comment cases.

git diff --check passed. Full CI runs on this PR.

Reject PostgreSQL E/e escape-string literals at the shared read-only query boundary so protected-column inspection cannot be bypassed.

Cover the reported exploit through DbAdmin and SqlKnowledgeReader, plus ordinary literals, comments and dollar quoting.

Fixes #612
@Sev7eNup
Sev7eNup merged commit d7e0bec into main Oct 24, 2026
17 checks passed
@Sev7eNup
Sev7eNup deleted the fix/612-sql-escape-string-guard branch October 24, 2026 16:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

PostgreSQL escape strings bypass sensitive-column checks in read-only SQL

1 participant