Exploit Deno KV storage?

[bdarcus]

This feature is currently available behind an unstable flag, but will be opened up with 2.0 this Summer.

https://deno.com/manual@v1.33.2/runtime/kv

Interestingly, there's a two-part key, so like namespace-prefixed-keys, which I believe they adopted for some security reasons, but is pretty elegant from a usage POV as well.

await kv.set(["users", "alice"], { birthday: "January 1, 1990" });
await kv.set(["users", "sam"], { birthday: "February 14, 1985" });
await kv.set(["users", "taylor"], { birthday: "December 25, 1970" });

// List out all entries with keys starting with `["users"]`
for await (const entry of kv.list({ prefix: ["users"] })) {
  console.log(entry.key);
  console.log(entry.value);
}

And then the value is just JSON.

The above code returns the following in the REPL:

[ "users", "alice" ]
{ birthday: "January 1, 1990" }
[ "users", "sam" ]
{ birthday: "February 14, 1985" }
[ "users", "taylor" ]
{ birthday: "December 25, 1970" }

So it could be used to store (and even serve) styles, templates, terms, input data, etc. Think examples like:

await kv.set(["template", "author-apa-full"], { ... });