Repository navigation
v0.2.0 — Security fix
Security fix (GHSA-55g5-vp25-phpg)
This release fixes an identifier-injection vulnerability and hardens the extension's security configuration. Community-extensions users on 0.1.0 should upgrade.
- Identifier injection in
apply_table_with— a crafted function name could break out of the reparsed table-function SQL and bypass the extension's own whitelist/blacklist. Injected identifiers are now quoted. Note this was never a privilege escalation against DuckDB:applyruns on the caller's own context and adds no reach beyond the caller's existing SQL. The whitelist is a guardrail for embedding scenarios, and that guardrail is what could be bypassed. - Security config is now per-session — the mode and whitelist/blacklist live in per-session state (
ClientContext) rather than process-global state, so one connection can't observe or mutate another's configuration, andfunc_apply_lock_security()binds the session that set it.
Regression test test/sql/func_apply_security_injection.test covers the injection bypass.
DuckDB v1.5.4
Built against DuckDB v1.5.4 (from v1.4.3). Stable builds are green on all platforms (Linux amd64/arm64, macOS amd64/arm64, Windows MSVC/mingw, Wasm ×3).
Known follow-up
The duckdb-next-build leg (DuckDB main/v1.6) does not yet compile — the v1.6 Identifier API migration (named-parameter vectors, Catalog::GetEntry) is tracked separately and does not affect this v1.5.4 release.