How accessing low-level C++ internal bindings via process.binding('fs') bypassed the experimental --permission --allow-fs-read flags.
Imagine a high-security office building with security guards at the front doors checking badges. A worker who doesn't have a badge walks around back, opens the maintenance door marked 'Internal Staff Only', and walks straight into the vault. In Node.js, the developer guarded the public JavaScript functions, but forgot to lock the underlying C++ internal door.
A developer runs untrusted code with node --permission --allow-fs-read=/tmp app.js.
The script invokes const binding = process.binding('fs');.
The script calls binding.open('/etc/passwd') directly, bypassing fs.readFile() wrappers.
The native C++ binding executes without permission checks, leaking confidential server files.
采用清晰易读的高级编程语言展示(不含晦涩汇编或二进制机器码)。
// VULNERABLE: src/node_file.cc before patch
static void Open(const FunctionCallbackInfo<Value>& args) {
Environment* env = Environment::GetCurrent(args);
// ROOT CAUSE:
// Only verified permissions if called through JS 'fs' module wrappers!
// Direct callers of process.binding('fs').open() evaded the check!
const char* path = *Utf8Value(env->isolate(), args[0]);
int fd = uv_fs_open(..., path, ...);
args.GetReturnValue().Set(fd);
}
// SECURE: src/node_file.cc patch
static void Open(const FunctionCallbackInfo<Value>& args) {
Environment* env = Environment::GetCurrent(args);
const char* path = *Utf8Value(env->isolate(), args[0]);
// 1. Enforce permission verification directly inside native C++ binding layer
if (env->permission()->is_enabled()) {
if (!env->permission()->is_granted(PermissionScope::kFileSystemRead, path)) {
THROW_ERR_ACCESS_DENIED(env, "Access to path %s denied by Permission Model", path);
return;
}
}
int fd = uv_fs_open(..., path, ...);
args.GetReturnValue().Set(fd);
}