You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[SECURITY] Bind request encodings in analytics cache freshness queries #822
A current-code test called SQLite TableOldestUpdateUTC against a disposable cache-shaped table. An ordinary missing request returned no counters; missing' OR 1=1 -- returned counters for a different request. This confirms a query boundary failure without needing raw native SQL. PostgreSQL's matching interpolation was source-reviewed, not runtime-tested here.
Required outcome
Bind requestEncoding using the existing backend parameter conventions, as IsTablePresent and QueryNamespaced already do.
Quote table/control identifiers using the shared safe identifier mechanism.
Preserve cache matching semantics and error visibility; syntax errors must not silently disguise a security-relevant cache mismatch.
Validation and acceptance
Add unit coverage for both dialects and black-box cached-provider queries using apostrophes, comment-like strings and backslashes in request parameters. Distinct encodings must never reuse another request's counters/results; repeated identical encodings should still hit cache.
Scope and related work
This is a cache freshness lookup, not the residual WHERE expression rendering issue. Both are CWE-89 but have different call sites and regression tests.
Activity