Contents

1 Overview ¶

This is a short tutorial on the RLBox API. If you are looking for a reference of all APIs, see [Doxygen]. If you are looking for motivation, see [RLBoxLogin], [RLBoxFirefox], and [RLBoxPaper].

RLBox is a toolkit for sandboxing third-party libraries. The toolkit consists of (1) a Wasm-based sandbox and (2) an API for retrofitting existing application code to interface with a sandboxed library. The Wasm-based sandbox is documented in its corresponding repository. While, the RLBox API can be used with different sandbox implementations, this documentation focuses on the API and the interface you will use when sandboxing code, independent of the underlying sandboxing mechanism.

Why do we need a sandboxing API? Sandboxing libraries without the RLBox API is both tedious and error-prone. This is especially the case when retrofitting an existing codebase like Firefox where libraries are trusted and thus the application-library boundary is blurry. To sandbox a library – and thus to move to a world where the library is no longer trusted – we need to modify this application-library boundary. For example, we need to add security checks in Firefox to ensure that any value from the sandboxed library is properly validated before it is used. Otherwise, the library (when compromised) may be able to abuse Firefox code to hijack its control flow (see [RLBoxPaper] for details). The RLBox API is explicitly designed to make retrofitting of existing application code simpler and less error-prone.

Sandboxing architecture overview As shown in Fig. 1, RLBox ensures that a sandboxed library is memory isolated from the rest of the application – the library cannot directly access memory outside its designated region – and that all boundary crossings are explicit. This ensures that the library cannot, for example, corrupt Firefox’s address space. It also ensures that Firefox cannot inadvertently expose sensitive data to the library (e.g., pointers that would leak its ASLR).

RLBox architecture — Fig. 1 Sandboxed libraries are isolated from the application and all communication between the sandboxed library and application code is mediated. This ensures that the application code is robust and does not use untrusted, tainted values without checking them.¶

Memory isolation is enforced by the underlying sandboxing mechanism (from the start, when you create the sandbox with create_sandbox()). Explicit boundary crossings are enforced by RLBox (either at compile- or and run-time). For example, with RLBox you can’t call library functions directly; instead, you must use the invoke_sandbox_function() method. Similarly, the library cannot call arbitrary Firefox functions; instead, it can only call functions that you expose with the register_callback() method. (To simplify the sandboxing task, though, RLBox does expose a standard library as described in 2.7 Standard library.)

When calling a library function, RLBox copies simple values into the sandbox memory before calling the function. For larger data types, such as structs and arrays, you can’t simply pass a pointer to the object. This would leak ASLR and, more importantly, would not work: sandboxed code cannot access application memory. So, you must explicitly allocate memory in the sandbox via malloc_in_sandbox() and copy application data to this region of memory (e.g., via strncpy).

RLBox similarly copies simple return values and callback arguments. Larger data structures, however, must (again) be passed by sandbox-reference, i.e., via a reference/pointer to sandbox memory.

To ensure that application code doesn’t use values that originate in the sandbox – and may thus be under the control of an attacker – unsafely, RLBox considers all such values as untrusted and taints them. Tainted values are essentially opaque values (though RLBox does provide some basic operators on tainted values). To use a tainted value, you must unwrap it by copying the value into application memory – and thus out of the reach of the attacker – and verifying it. Indeed, RLBox forces application code to perform the copy and verification in sync using verifiction functions.

1.1 Example library sandboxing ¶

To get a feel for what it’s like to use RLBox, we’re going to sandbox a tiny library mylib that has four functions:

// mylib.c:

void hello() {
   printf("Hello world from mylib\n");
}

unsigned add(unsigned a, unsigned b) {
   return a + b;
}

void echo(const char* str) {
   printf("> mylib: %s\n", str);
}

void call_cb(void (*cb) (const char* str)) {
   cb("hi again!");
}

int get_error_code() {
   return 0;
}

This is not the most interesting library, security-wise, but it is complicated enough to demonstrate various RLBox features.

To get started, in our main application file let’s first import the RLBox library:

// main.cpp:

#define RLBOX_SINGLE_THREADED_INVOCATIONS
#define RLBOX_USE_STATIC_CALLS() rlbox_noop_sandbox_lookup_symbol

#include <stdio.h>
#include "mylib.h"
#include "rlbox.hpp"
#include "rlbox_noop_sandbox.hpp"

using namespace rlbox;
...

In our main function, let’s now create a new sandbox (for this example we’re going to use the NULL sandbox) and call the hello function:

...
int main(int argc, char const *argv[]) {

   // Create a new sandbox
   rlbox::rlbox_sandbox<rlbox_noop_sandbox> sandbox;
   sandbox.create_sandbox();

   // call the library hello function
   sandbox.invoke_sandbox_function(hello);
...

Note that we do not call hello() directly. Instead, we use the invoke_sandbox_function() method. We can similarly call the add function:

...
   // call the add function and check the result:
   auto ok = sandbox.invoke_sandbox_function(add, 3, 4).copy_and_verify([](unsigned ret){
         printf("Adding... 3+4 = %d\n", ret);
         return ret == 7;
   });
   printf("OK? = %d\n", ok);
...

This invocation is a bit more interesting. First, we call add with arguments. Second, RLBox ensures that the unsigned return value that add returns is tainted and thus cannot be used without verification. Here, we call the copy_and_verify function which copies the value into application memory and runs our verifier function:

[](unsigned ret){
      printf("Adding... 3+4 = %d\n", ret);
      return ret == 7;
}

This lambda simply prints the tainted value and returns true if it is 7. A compromised library could return any value and if we use this value to, say, index an array this could potentially introduce an out-of-bounds memory access.

Let’s now call the echo function which takes a slightly more interesting argument: a string. Here, we can’t simply pass a string literal as an argument: the sandbox cannot access application memory where this would be allocated. Instead, we must allocate a buffer in sandbox memory and copy the string we want to pass to echo into this region:

...
   const char* helloStr = "hi hi!";
   size_t helloSize = strlen(helloStr) + 1;
   // allocate memory in the sandbox:
   auto taintedStr = sandbox.malloc_in_sandbox<char>(helloSize);
   // copy helloStr into the sandbox:
   std::strncpy(taintedStr.unverified_safe_pointer_because(helloSize, "writing to region"), helloStr, helloSize);
...

Here taintedStr is actually a tainted string: it lives in the sandbox memory and could be written to by the (compromised) library code concurrently. As such, it’s unsafe for us to use this pointer without verification. Above, we use the “unverified_safe_pointer_because” verifier which basically removes the taint without any verification. This is safe because we copy the helloStr to sandbox memory: at worst, the sandboxed library can overwrite the memory region pointed to by taintedStr and crash when it tries to print it.

Note that the string “writing to region” does not have any special meaning in the code. Rather the RLBox API asks you to provide a free-form string that acts as documentation. Essentially you are providing a string saying “it is safe to remove the tainting from this type because …”. Such documentation may be useful to other developers who read your code. As discussed, in the above example, a write to the region cannot cause a memory safety error in the application”.

Now, we can just call the function and free the allocated string:

...
   sandbox.invoke_sandbox_function(echo, taintedStr);
   sandbox.free_in_sandbox(taintedStr);
...

Finally, let’s call the call_cb function. To do this, let’s first define a callback for the function to call. We define this function above the main function:

...
void hello_cb(rlbox_sandbox<rlbox_noop_sandbox>& _,
            tainted<const char*, rlbox_noop_sandbox> str) {
   auto checked_string =
      str.copy_and_verify_string([](std::unique_ptr<char[]> val) {
         return std::strlen(val.get()) < 1024 ? std::move(val) : nullptr;
      });
   printf("hello_cb: %s\n", checked_string.get());
}
...

This callback is called with a string. We thus call the string verification function with a simple verifier:

...
   [](std::unique_ptr<char[]> val) {
        return std::strlen(val.get()) < 1024 ? std::move(val) : nullptr;
    }
...

This verifier moves the string if it’s length is less than 1KB and otherwise returns the nullptr. In the callback we simply print this (potentially null) string.

Let’s now continue in main, register the callback – otherwise RLBox will disallow the library-application call – and pass the callback to the call_cb function:

...
   // register callback and call it
   auto cb = sandbox.register_callback(hello_cb);
   sandbox.invoke_sandbox_function(call_cb, cb);

   // `cb` is unregistered automatically once it goes out of scope
   // Once unregistered, the callback cannot be invoked any further
   // We can also manually unregister it if we want to unregister it sooner
   cb.unregister();
...

Finally, let’s destroy the sandbox and exit:

...
   // destroy sandbox
   sandbox.destroy_sandbox();

   return 0;
}

2 Core API ¶

In this section we describe a large part of the RLBox API you are likely to encounter when porting libraries. The API has some more advanced features and types that are necessary but not as commonly used (see [Doxygen]). In most cases the RLBox type system will give you an informative error if and how to use these features.

2.1 Creating (and destroying) sandboxes ¶

RLBox encapsulates sandboxes with rlbox_sandbox class. For now, RLBox supports two sandboxes: a Wasm-based sandboxed and the null sandbox. The null sandbox doesn’t actually enforce any isolation, but is very useful for migrating an existing codebase to use the RLBox API. In fact, in most cases you want to port the existing code to use RLBox when interfacing with a particular library and only then switch over to the Wasm-based sandbox.

template<typename T_Sbx> class rlbox_sandbox : protected T_Sbx ¶

Encapsulation for sandboxes.

tparam T_Sbx: Type of sandbox. For the null sandbox this is rlbox_noop_sandbox

class rlbox_noop_sandbox¶: Class that implements the null sandbox. This sandbox doesn’t actually provide any isolation and only serves as a stepping stone towards migrating an application to use the RLBox API.

template<typename ...T_Args> inline bool rlbox::rlbox_sandbox::create_sandbox(T_Args... args)¶

Create a new sandbox.

Template Parameters: T_args – Arguments passed to the underlying sandbox implementation. For the null sandbox, no arguments are necessary.

Creating sandboxes is mostly straightforward. For the null sandbox, however, you need to add a #define at the top of your entry file, before you include the RLBox headers:

#define RLBOX_USE_STATIC_CALLS() rlbox_noop_sandbox_lookup_symbol
...
rlbox::rlbox_sandbox<rlbox_noop_sandbox> sandbox;
sandbox.create_sandbox();

inline auto rlbox::rlbox_sandbox::destroy_sandbox()¶: Destroy sandbox and reclaim any memory.

It’s important to destroy a sandbox after you are done with it. This ensures that the memory footprint of sandboxing remains low. Once you destroy a sandbox though, it is an error to use the sandbox object.

2.2 Calling sandboxed library functions ¶

RLBox disallows code from calling sandboxed library functions directly. Instead, application code must use the invoke_sandbox_function() method.

invoke_sandbox_function(func_name, ...)¶

Call sandbox function.

Parameters

func_name – The sandboxed library function to call.
... – Arguments to function should be simple or tainted values.

Returns

Tainted value or void.

Though this function is defined via macros, RLBox uses some template and macro magic to make this look like a sandbox method. So, in general, you can call sandboxed library functions as:

// call foo(4)
auto result = sandbox.invoke_sandbox_function(foo, 4);

2.3 Exposing functions to sandboxed code ¶

Application code can expose callback functions to sandbox via register_callback(). These functions can be called by the sandboxed code until they (1) are no longer in scope or (2) are explicitly unregistered via the unregister() function.

The type signatures of register_callback() function is a bit daunting. In short, the function takes a callback function and returns a function pointer that can be passed to the sandbox (e.g., via invoke_sandbox_function()).

A callback function is a function that has a special type:

The first argument of the function must be a reference a sandbox object.
The remaining arguments must be tainted.
The return value must be tainted or void. This ensures that the application cannot accidentally leak data to the sandbox.

Forcing arguments to be tainted forces the application to handled values coming from the sandbox with care. Dually, the return type ensures that the application cannot accidentally leak data to the sandbox.

2.4 Tainted values ¶

Values that originate in the sandbox are tainted. We use a special tainted type tainted to encapsulate such values and prevent the application from using tainted values unsafely.

template<typename T, typename T_Sbx> class tainted¶

RLBox has several kinds of tainted values, beyond tainted. Thse, however, are slightly less pervasive in the surface API.

template<typename T, typename T_Sbx> class tainted_volatile : public rlbox::tainted_base_impl<tainted_volatile, T, T_Sbx>¶: Tainted volatile values are like tainted values but still point to sandbox memory. Dereferencing a tainted pointer produces a tainted_volatile.

class tainted_boolean_hint¶: Tainted boolean value that serves as a “hint” and not a definite answer. Comparisons with a tainted_volatile return such hints. They are not tainted<bool> values because a compromised sandbox can modify tainted_volatile data at any time.

2.4.1 Unwrapping tainted values ¶

To use tainted values, the application can copy the value to application memory, verify the value, and unwrap it. RLBox provides several functions to do this.

Warning

doxygenfunction: Unable to resolve function “copy_and_verify” with arguments None in doxygen xml output for project “RLBox” from directory: /home/d/hack/rlbox_sandboxing_api/docs/doxygen/xml. Potential matches:

- template<typename T = void> bool copy_and_verify(...) const
- template<typename T = void> int copy_and_verify(...) const
- template<typename T_Func> auto copy_and_verify(T_Func verifier) const

For a given tainted type, the verifier should have the following signature:

Tainted type kind	Example type	Example verifier
Simple type	`int`	`T_Ret(*)(int)`
Pointer to simple type	`int*`	`T_Ret(*)(unique_ptr<int>)`
Pointer to class type	`Foo*`	`T_Ret(*)(unique_ptr<Foo>)`
Pointer to array	`int[4]`	`T_Ret(*)(std::array<int, 4>)`
Class type	`Foo`	`T_Ret(*)(tainted<Foo>)`

In general, the return type of the verifier T_Ret is not constrained and can be anything the caller chooses.

template<typename T_Func> inline auto rlbox::tainted_base_impl::copy_and_verify_range(T_Func verifier, std::size_t count) const¶

Copy a range of tainted values from sandbox and verify them.

Parameters

verifer – Function used to verify the copied value.
count – Number of elements to copy.

Template Parameters

T_Func – the type of the verifier. If the tainted type is int* then T_Func = T_Ret(*)(unique_ptr<int[]>).

Returns

Whatever the verifier function returns.

template<typename T_Func> inline auto rlbox::tainted_base_impl::copy_and_verify_string(T_Func verifier) const¶

Copy a tainted string from sandbox and verify it.

Parameters: verifer – Function used to verify the copied value.
Template Parameters: T_Func – the type of the verifier either T_Ret(*)(unique_ptr<char[]>) or T_Ret(*)(std::string)
Returns: Whatever the verifier function returns.

template<typename T_Func> inline auto rlbox::tainted_base_impl::copy_and_verify_address(T_Func verifier)¶

Copy a tainted pointer from sandbox and verify the address.

This function is useful if you need to verify physical bits representing the address of a pointer. Other APIs such as copy_and_verify performs a deep copy and changes the address bits.

Parameters: verifier – Function used to verify the copied value.
Template Parameters: T_Func – the type of the verifier T_Ret(*)(uintptr_t)
Returns: Whatever the verifier function returns.

In some cases it’s useful to unwrap tainted values without verification. Sometimes this is safe to do and RLBox provides a method for doing so called unverified_safe_because

Since pointers are special (sandbox code may modify the data the pointer points to), we have a similar function for pointers called unverified_safe_pointer_because. This API requires specifying the number of elements being pointed to for safety.

We however provide additional functions that are especially useful during migration:

template<template<typename, typename> typename T_Wrap, typename T, typename T_Sbx> class rlbox::tainted_base_impl¶

Public Functions

inline auto UNSAFE_unverified()¶: Unwrap a tainted value without verification. This is an unsafe operation and should be used with care.

inline auto UNSAFE_sandboxed(rlbox_sandbox<T_Sbx> &sandbox)¶

Like UNSAFE_unverified, but get the underlying sandbox representation.

For the Wasm-based sandbox, this function additionally validates the unwrapped value against the machine model of the sandbox (LP32).

Parameters: sandbox – Reference to sandbox.

These functions are also available for callback

Danger

Unchecked unwrapped tainted values can be abused by a compromised or malicious library to potentially compromise the application.

2.4.2 Operating on tainted values ¶

Unwrapping tainted values requires care – getting a verifier wrong could lead to a security vulnerability. It’s also not cheap: we need to copy data to the application memory to ensure that the sandboxed code cannot modify the data we’re tyring to verify. Lucikly, it’s not always necessary to copy and verify: sometimes we can compute on tainted values directly. To this end, RLBox defines different kinds of operators on tainted values, which produce tainted values. This allows you to perform some computations on tainted values, pass the values back into the sandbox, and only later unwrap a tainted value when you need to. operators like + and - on tainted values.

Class of operator	Supported operators
Arithmetic operators	`=`, `+`, `-`, `*`, `/`, `%`, `++`, `--`
Relational operators	`==`, `!=`, `<`, `<=`, `>`, `>=`
Logical operators	`!`, `&&` (limited), `\|\|` (limited)
Bitwise operators	`~`, `&`, `\|`, `^`, `<<`, `>>`
Compound operators	`+=`, `-=`, `*=`, `/=`, `%=`, `&=`, `\|=`, `^=`, `<<=`, `>>=`
Pointer operators	`[]`, `*`, `&`, `->`

When applying a binary operator like << to a tainted value and an untainted values the result is always tainted.

RLBox also defines several comparison operators on tainted values that sometime unwrap the result:

Operators ==, != on tainted pointers is allowed if the rhs is nullptr_t and return unwrapped bool.
Operator ! on tainted pointers retruns an unwrapped bool.
Operators ==, !=, ! on non-pointer tainted values return a tainted<bool>
Operators ==, !=, ! on tainted_volatile values returns a tainted_boolean_hint
Operators && and || on booleans are only permitted when arguments are variables (not expressions). This is because C++ does not permit safe overloading of && and || operations with expression arguments as this affects the short circuiting behaviour of these operations.

2.5 Application-sandbox shared memory ¶

Since sandboxed code cannot access application memory, to share objects across the boundary you need to explicitly allocate memory that both the application and sandbox can access. To this end, malloc_in_sandbox() allocates memory within the sandbox region and returns a tainted pointer that can be used by both the application and sandbox (e.g., by passing the pointer as an argument to a function).

template<typename T> inline tainted<T*, T_Sbx> rlbox::rlbox_sandbox::malloc_in_sandbox()¶

Allocate a new pointer that is accessible to both the application and sandbox. The pointer is allocated in sandbox memory.

Template Parameters: T – The type of the pointer you want to create. If T=int, this would return a pointer to an int.
Returns: tainted<T*, T_Sbx> Tainted pointer accessible to the application and sandbox.

template<typename T> inline tainted<T*, T_Sbx> rlbox::rlbox_sandbox::malloc_in_sandbox(uint32_t count)¶

Allocate an array that is accessible to both the application and sandbox. The pointer is allocated in sandbox memory.

Template Parameters: T – The type of the array elements you want to create. If T=int, this would return a pointer to an array of ints.
Parameters: count – The number of array elements to allocate.
Returns: tainted<T*, T_Sbx> Tainted pointer accessible to the application and sandbox.

Manually allocated memory is freed explicitly:

template<typename T> inline void rlbox::rlbox_sandbox::free_in_sandbox(tainted<T*, T_Sbx> ptr)¶

Free the memory referenced by the tainted pointer.

Parameters: ptr – Pointer to sandbox memory to free.

2.6 Migrating code by temporarily removing tainting ¶

RLBox is designed to simplify working with existing applications/code bases. Rather than migrating an application to use RLBox’s APIs in a single shot, RLBox allows “incremental migration” to simplify this step. In particular, migrating existing code to use RLBox APIs i.e. using tainted types and replacing function calls to libraries with invoke_sandbox_function() method, can be performed one line at a time. After each such migration, you can continue to build, run/test the program with full functionality to make sure the migration step is correct.

For example consider migrating some existing code that uses mylib:

// app.c:

void print_error_message() {
   char* msgs[] = { "Success", "Fail" };
   int result = get_error_code();
   printf("Result: %s\n", msgs[result]);
   ...
}

Rather than migrating the full function to use RLBox, you can migrate just the call to get_error_code by leveraging the UNSAFE_unverified APIs to removing the tainting:

// app.c:

void print_error_message() {
   char* msgs[] = { "Success", "Fail" };

   // Migrate this line to use the RLBox API
   tainted<int, rlbox_noop_sandbox> tainted_result = get_error_code();
   int result = tainted_result.UNSAFE_unverified();

   // Not migrated
   printf("Result: %s\n", msgs[result]);
   ...
}

Observe that by renaming variables, we can easily leave the other lines of code unmodified. After building and testing this step, we can now migrate the line that prints the message:

// app.c:

void print_error_message() {
   char* msgs[] = { "Success", "Fail" };

   // Migrate this line to use the RLBox API
   auto tainted_result = get_error_code();

   // Not migrated
   printf("Result: %s\n", msgs[tainted_result.UNSAFE_unverified()]);

   int result = tainted_result.UNSAFE_unverified();
   ...
}

Similarly, we can proceed with replacing all uses of result in the ... portion of code as well.

As the “UNSAFE” portion of the UNSAFE_unverified API indicates, migration is NOT complete until we replace the uses of UNSAFE_unverified with copy_and_verify or unverified_safe_because as discussed in 2.4.1 Unwrapping tainted values. Here, the since tainted_result is being used to access an array of size 2, we can verify it as shown below:

printf("Result: %s\n", msgs[tainted_result.copy_and_verify([](int val){
   if (val < 0 or val >= 2) { abort(); }
   return val;
}));

The exact opposite of the UNSAFE_unverified function i.e. converting regularly “untainted” data to tainted is also available:

Tainted type kind	Example type	Converted type	Conversion API
Simple type	`int`	`tainted<int, rlbox_noop_sandbox>`	Automatic conversion. No code change needed.
Pointer to type	`Foo*`	`tainted<Foo*, rlbox_noop_sandbox>`	`sandbox.UNSAFE_accept_pointer(ptr)`

2.7 Standard library ¶

RLBox provides several helper functions to application for handling tainted data (memory influenced by or located in sandoxed regions) similar to the C/C++ standard library. We list a few of these below; they operate similar to the standard library equivalents, but they accept tainted data.

template<typename T_Sbx, typename T_Rhs, typename T_Val, typename T_Num, template<typename, typename> typename T_Wrap> inline T_Wrap<T_Rhs*, T_Sbx> rlbox::memset(rlbox_sandbox<T_Sbx> &sandbox, T_Wrap<T_Rhs*, T_Sbx> ptr, T_Val value, T_Num num)¶: Fill sandbox memory with a constant byte.

template<typename T_Sbx, typename T_Rhs, typename T_Lhs, typename T_Num, template<typename, typename> typename T_Wrap> inline T_Wrap<T_Rhs*, T_Sbx> rlbox::memcpy(rlbox_sandbox<T_Sbx> &sandbox, T_Wrap<T_Rhs*, T_Sbx> dest, T_Lhs src, T_Num num)¶: Copy to sandbox memory area. Note that memcpy is meant to be called on byte arrays does not adjust data according to ABI differences. If the programmer does accidentally call memcpy on buffers that needs ABI adjustment, this may cause compatibility issues, but will not cause a security issue as the destination is always a tainted or tainted_volatile pointer.

template<typename T_Lhs, typename T_Rhs, typename T_Sbx, template<typename, typename> typename T_Wrap> inline tainted<T_Lhs, T_Sbx> rlbox::sandbox_reinterpret_cast(const T_Wrap<T_Rhs, T_Sbx> &rhs) noexcept¶: The equivalent of a reinterpret_cast but operates on sandboxed values.

template<typename T_Lhs, typename T_Rhs, typename T_Sbx, template<typename, typename> typename T_Wrap> inline tainted<T_Lhs, T_Sbx> rlbox::sandbox_const_cast(const T_Wrap<T_Rhs, T_Sbx> &rhs) noexcept¶: The equivalent of a const_cast but operates on sandboxed values.

template<typename T_Lhs, typename T_Rhs, typename T_Sbx, template<typename, typename> typename T_Wrap> inline tainted<T_Lhs, T_Sbx> rlbox::sandbox_static_cast(const T_Wrap<T_Rhs, T_Sbx> &rhs) noexcept¶: The equivalent of a static_cast but operates on sandboxed values.

RLBox also provides helper functions for allocating memory in the sandbox (resp application) and transferring it from the application (resp sandbox) with:

template<typename T_Sbx, typename T> tainted<T*, T_Sbx> rlbox::copy_memory_or_grant_access(rlbox_sandbox<T_Sbx> &sandbox, T *src, size_t num, bool free_source_on_copy, bool &copied)¶

This function either.

copies the given buffer into the sandbox calling delete on the src OR
if the sandbox allows, adds the buffer to the existing sandbox memory

Parameters

sandbox – Target sandbox
src – Raw pointer to the buffer
num – Number of bytes in the buffer
free_source_on_copy – If the source buffer was copied, this variable controls whether copy_memory_or_grant_access should call delete on the src. This calls delete[] if num > 1.
copied – out parameter indicating if the source was copied or transfered

template<typename T_Sbx, typename T, template<typename, typename> typename T_Wrap> T *rlbox::copy_memory_or_deny_access(rlbox_sandbox<T_Sbx> &sandbox, T_Wrap<T*, T_Sbx> src, size_t num, bool free_source_on_copy, bool &copied)¶

This function either.

copies the given buffer out of the sandbox calling free_in_sandbox on the src OR
if the sandbox allows, moves the buffer out of existing sandbox memory

Parameters

sandbox – Target sandbox
src – Raw pointer to the buffer
num – Number of bytes in the buffer
free_source_on_copy – If the source buffer was copied, this variable controls whether copy_memory_or_grant_access should call delete on the src. This calls delete[] if num > 1.
copied – out parameter indicating if the source was copied or transfered

These functions copy when using a sandbox like Wasm. For the nop-sandbox, they don’t copy and only move pointers, though.

3 Handling more complex ABIs ¶

3.1 Passing structs to/from a sandbox ¶

RLBox currently doesn’t automatically let you use fields of structs. To use fields of a tainted struct you need to essentially tell RLBox about the struct type and layout. You typically do this in a separate header file and include this file in your application code as follows:

// app code:

#include "lib_struct_file.h"
rlbox_load_structs_from_library(mylib);

The first line includes the header file (we will populate shortly). The second line loads the struct definitions using the library name mylib.

Let’s suppose our library has two structs:

// mylib.h:

struct Inner {
   int val;
};

struct Foo {
   unsigned char[5] status_array;
   Inner internal;
   unsigned int width;
};

In _lib_struct_file.h you will then provide a definition for Foo alone would be as follows:

...
#define sandbox_fields_reflection_mylib_class_Foo(f, g, ...)         \
  f(unsigned char[5], status_array, FIELD_NORMAL, ##__VA_ARGS__) g() \
  f(Inner, internal, FIELD_NORMAL, ##__VA_ARGS__) g()                \
  f(unsigned int, width, FIELD_NORMAL, ##__VA_ARGS__) g()

#define sandbox_fields_reflection_mylib_allClasses(f, ...)  \
  f(Foo, mylib, ##__VA_ARGS__)
...

Since Foo has an Inner struct, though, we’ll need to also provide a definition for this struct if we want to access the val value:

...
#define sandbox_fields_reflection_mylib_class_Inner(f, g, ...)    \
  f(int, val, FIELD_NORMAL, ##__VA_ARGS__) g()

#define sandbox_fields_reflection_mylib_class_Foo(f, g, ...)         \
  f(unsigned char[5], status_array, FIELD_NORMAL, ##__VA_ARGS__) g() \
  f(Inner, internal, FIELD_NORMAL, ##__VA_ARGS__) g()                \
  f(unsigned int, width, FIELD_NORMAL, ##__VA_ARGS__) g()

#define sandbox_fields_reflection_mylib_allClasses(f, ...)  \
  f(Inner, mylib, ##__VA_ARGS__)                            \
  f(Foo, mylib, ##__VA_ARGS__)
...

Each struct file is intended to hold all struct definitions associated with a library.

Danger

The compiler currently doesn’t catch type mismatches, missing members, or incorrectly ordered members in the struct definition.

Take a look at the ogg struct layout in Firefox for a complete example.

In the future we will likely generate these kinds of files automatically.

3.2 Invoking varargs functions ¶

RLBox does not (yet) support calling functions with variable arguments currently. So, if the library you are sandboxing has APIs with variable arguments you need to monomorphize the usages. Specifically, you need to create wrapper functions for each usage you wish to expose. Consider the following example:

// Original library function:
int example_call(int x, int y, ...);

...

// Original invocations in application code:
rv = example_call(x, y, RESET_FLAG);
rv = example_call(x, y, INVERT_FLAG, 'c');

One way to handle this in RLBox is to expose two functions as follows:

int example_call_reset(int x, int y, uint8_t flag) {
   return example_call(x, y, flag);
}

int example_call_invert(int x, int y, uint8_t flag, char c) {
   return example_call(x, y, flag, c);
}

Then, you can call them as usual:

rv = sandbox.invoke_sandbox_function(example_call_reset, x, y, RESET_FLAG);
rv = sandbox.invoke_sandbox_function(example_call_invert, x, y, INVERT_FLAG, 'c');

3.3 Invoking C++ functions in a sandbox ¶

RLBox does not currently let you invoke C++ library functions directly. Instead you need to expose a C ABI. Functions are largely straightforward. Methods require a bit of work since the receiver object is implicit: The simplest way to do this for class methods is to expose C functions and just pass a pointer to the receiver object as the first argument.

3.4 Passing application pointers into the sandbox with app_pointer ¶

It’s sometimes useful to pass application pointers into the sandbox. For example, you may need to pass a pointer to the receiver (this) so sandbox library can pass this pointer back in a callback. We can’t trust the sandbox with actual applications pointers. RLBox instead provides a level of indirection.

If you want to pass a pointer into the sandbox you can use the get_app_pointer() <get_app_pointer> API, which returns an app_pointer. For example, in the expat library we need to pass a pointer to the receiver:

mAppPtr = mSandbox->get_app_pointer(static_cast<void*>(this));
// convert the app_pointer to tainted
tainted_expat<void*> t_driver = mAppPtr.to_tainted();
// call function as usual:
mSandbox->invoke_sandbox_function(..., t_driver);

where mAppPtr is a member of the class:

app_pointer_expat<void*> mAppPtr;

Internally, RLBox keeps a map between app pointers and the corresponding tainted pointers exposed to the sandbox. This lets you lookup the pointers in callbacks, for example:

void callback(rlbox_sandbox_expat& aSandbox, ... tainted_expat<void*> t_driver) {
  nsExpatDriver* self = aSandbox.lookup_app_ptr(rlbox::sandbox_static_cast<nsExpatDriver*>(t_driver));

Like callbacks, you need to keep app pointers alive and unregister them when you’re done:

mAppPtr.unregister();

4 Additional material ¶

Here is some additional material on how to use RLBox.

A good next step after this tutorial is to get hands-on migrating an application to using a library that you want to sandbox. The simple library example repo is a “toy” application that uses a potentially “buggy” library. Try migrating the application to use the RLBox API based on what you’ve learnt in this tutorial. The solution is available in the solution folder in the same repo.
Here is an alternate short tutorial on using the RLBox APIs. Note that this tutorial uses an alternate RLBox sandbox plugin (which uses the Lucet Wasm compiler and RLBox plugin rather than the wasm2c based plugin recommended in this tutorial, but this does not affect the use of the RLBox APIs themselves).
Another useful example of using the RLBox APIs is the RLBox test suite itself.
You can also see usage of the RLBox APIs in the Firefox browser by using the Firefox code search.
Finally, the academic paper discussing the development of RLBox and its use in Firefox [RLBoxPaper] at the USENIX Security conference 2020 and the accompanying video explanations are a good way to get an overview of RLBox.

5 References ¶

RLBoxPaper(1,2): Retrofitting Fine Grain Isolation in the Firefox Renderer by S. Narayan, C. Disselkoen, T. Garfinkel, S. Lerner, H. Shacham, D. Stefan
RLBoxLogin: The Road to Less Trusted Code: Lowering the Barrier to In-Process Sandboxing
RLBoxFirefox: Securing Firefox with WebAssembly by N. Froyd
Doxygen(1,2): RLBox Doxygen Documentation

1 Overview ¶

1.1 Example library sandboxing ¶

2 Core API ¶

2.1 Creating (and destroying) sandboxes ¶

2.2 Calling sandboxed library functions ¶

2.3 Exposing functions to sandboxed code ¶

2.4 Tainted values ¶

2.4.1 Unwrapping tainted values ¶

2.4.2 Operating on tainted values ¶

2.5 Application-sandbox shared memory ¶

2.6 Migrating code by temporarily removing tainting ¶

2.7 Standard library ¶

3 Handling more complex ABIs ¶

3.1 Passing structs to/from a sandbox ¶

3.2 Invoking varargs functions ¶

3.3 Invoking C++ functions in a sandbox ¶

3.4 Passing application pointers into the sandbox with app_pointer ¶

4 Additional material ¶

5 References ¶

6 Indices and tables ¶

RLBox Sandboxing API

Navigation

Related Topics