content-security-policy icon indicating copy to clipboard operation
content-security-policy copied to clipboard

Extending WASM CSP to be covered under `strict-dynamic`

Open jeremie-stripe opened this issue 5 months ago • 0 comments

In the current specification, it's mentioned that WebAssembly is only integrated with the unsafe-eval and wasm-unsafe-eval stanza for script-src.

Separately, there is also a mode of CSP known as strict-dynamic which allows trust to be given specifically to certain scripts which then carry that trust to (mostly) anything else they would execute dynamically.

Today it seems like this trust is extended to both scripts and worker generated by the initial trusted script but crucially not to WebAssembly code that is attempted to be instantiated from a trust script in this way.

Is this a desired aspect of the specification or something to fix?

jeremie-stripe avatar Sep 05 '24 15:09 jeremie-stripe