沙箱与权限
实施策略，进一步限制 WASM 模块的能力，并管理其在宿主环境中的权限
沙箱与权限 是 CoddyKit 上的免费 WebAssembly (WASM) for High Performance Apps 课时。 这是第 2 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 WebAssembly (WASM) for High Performance Apps 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 WebAssembly (WASM) for High Performance Apps 课程共包含 4 节课。
本课时的部分内容尚未翻译，以英文显示。
WASM's Security Sandbox
WebAssembly (WASM) is designed with security at its core. It operates within a tightly controlled environment known as a sandbox.
This sandboxing mechanism isolates WASM code from the host system, preventing it from directly accessing sensitive resources or executing arbitrary operations outside its allocated space.
Inherent Restrictions
By default, a WASM module has no direct access to common system capabilities such as:
- The host's file system
- Network interfaces
- Environment variables
- Arbitrary memory outside its linear memory
This strict isolation is a fundamental security feature, making WASM a safe choice for executing untrusted code.
Granting Powers via Imports
If a WASM module needs to perform tasks like logging, accessing a file, or making a network request, it cannot do so directly. Instead, it must import functions from its host environment.
The host (e.g., a web browser's JavaScript engine or a WASI runtime) acts as a gatekeeper, explicitly providing these capabilities. This gives the host full control over what the WASM module can and cannot do.
WASM Requests Host Functions
Here's how a Rust-compiled WASM module might declare its need for a host function. It expects the host to provide a function called host_log within the env module.
/* src/lib.rs */
// Link to an imported function from the 'env' module
#[link(wasm_import_module = "env")]
extern "C" {
fn host_log(ptr: *const u8, len: usize);
}
#[no_mangle]
pub extern "C" fn log_message_from_wasm() {
let message = "Hello from WASM!";
let ptr = message.as_ptr();
let len = message.len();
unsafe {
// Call the imported host function
host_log(ptr, len);
}
}Host Grants or Denies Permission
The JavaScript host decides whether to provide the host_log function. If it's provided, WASM can call it. If not, the WASM module will fail to instantiate, enforcing the permission.
Try running this example:
// host.js
async function loadWasmWithPermission() {
const wasmBytes = await fetch("log_module.wasm").then(res => res.arrayBuffer());
// Define the imports object for WASM
const imports = {
env: {
host_log: (ptr, len) => {
// This function is provided by JS to WASM
const memory = instance.exports.memory;
const data = new Uint8Array(memory.buffer, ptr, len);
const text = new TextDecoder("utf-8").decode(data);
console.log(`WASM says: ${text}`);
}
}
};
try {
const { instance } = await WebAssembly.instantiate(wasmBytes, imports);
instance.exports.log_message_from_from_wasm(); // Call the WASM function
} catch (e) {
console.error("WASM instantiation failed:", e);
}
}
loadWasmWithPermission();Controlling WASM Memory
Beyond functions, the host environment also controls the WASM module's linear memory. When instantiating a module, the host can specify the initial and maximum memory size (in 64KB pages).
This prevents a malicious or buggy WASM module from consuming excessive memory and impacting the host application.
// host.js
async function loadWasmWithMemory() {
// Create a WebAssembly.Memory object
const memory = new WebAssembly.Memory({ initial: 1, maximum: 2 });
// 1 page (64KB) initial, max 2 pages (128KB)
const wasmBytes = await fetch("memory_user.wasm").then(res => res.arrayBuffer());
const imports = {
env: {
memory: memory // Pass the controlled memory object to WASM
}
};
const { instance } = await WebAssembly.instantiate(wasmBytes, imports);
console.log("WASM module loaded with controlled memory.");
// WASM can now access and grow this memory up to 2 pages
}
loadWasmWithMemory();Principle of Least Privilege
A critical security practice when working with WASM is the Principle of Least Privilege.
This means you should grant a WASM module only the permissions and resources it absolutely needs to perform its intended function, and no more. Minimizing access reduces the attack surface and potential impact of vulnerabilities.
Beyond Browser: WASI & Host Capabilities
For environments outside the web browser (like servers or IoT devices), the WebAssembly System Interface (WASI) standardizes system-level access.
Even with WASI, the underlying WASI runtime (e.g., Wasmtime, Wasmer) is the host. It still enforces permissions, deciding which file paths, network sockets, or environment variables a WASI module can access.
Secure Interaction Tips
To build secure WASM applications:
- Minimize Imports: Only provide host functions that are strictly necessary.
- Validate Inputs: Always validate data passed from WASM to JavaScript (and vice-versa) to prevent injection or buffer overflow issues.
- Memory Boundaries: Set appropriate initial and maximum memory limits.
- Trusted Modules: Only load WebAssembly modules from trusted and verified sources.
Permission Check
Consider a WebAssembly module that needs to read from a specific file. Which entity is primarily responsible for granting or denying this capability?
Recap: Secure WASM
We've learned that WebAssembly modules operate within a secure sandbox, relying entirely on the host environment to provide any external capabilities. Managing imports and controlling memory are crucial for maintaining security and adhering to the principle of least privilege.
Understanding these mechanisms helps you build robust, high-performance, and secure WebAssembly applications.
常见问题解答
「沙箱与权限」课时是免费的吗？
是的 — 「沙箱与权限」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 WebAssembly (WASM) for High Performance Apps 课程的其余内容，请升级到 CoddyKit PRO。 WebAssembly (WASM) for High Performance Apps 课程共包含 4 节课。
「沙箱与权限」这节课中我会学到什么？
实施策略，进一步限制 WASM 模块的能力，并管理其在宿主环境中的权限 你通过在浏览器中直接运行的动手代码来练习 WebAssembly (WASM) for High Performance Apps，全天候 AI 导师会在你学习这节课的过程中回答你的问题。
学习 WebAssembly (WASM) for High Performance Apps 需要有经验吗？
无需任何先前经验。CoddyKit 上的 WebAssembly (WASM) for High Performance Apps 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 2 节课，共 4 节。
「沙箱与权限」课时需要多长时间？
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。
我能在这节 WebAssembly (WASM) for High Performance Apps 课中编写并运行代码吗？
能。每节 WebAssembly (WASM) for High Performance Apps 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。