User-level segmentation mechanism that facilitates safely executing untrusted native code

• US 8,136,158 B1
• Filed: 08/29/2008
• Issued: 03/13/2012
• Est. Priority Date: 07/21/2008
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Sehr, David C., Chen, J. Bradley, Yee, Bennet S.
• Primary Examiner(s): Shiferaw, Eleni
• Assistant Examiner(s): ABYANEH, ALI S
• Application Number:
  US12/202,083
• Time in Patent Office: 1,292 Days
• Field of Search: 726/22, 713/2, 713/188
• US Class Current: 726/22
• CPC Class Codes: G06F 12/1491 in a hierarchical protection system, e.g. privilege levels, memory rings
• CPC Class Codes: G06F 21/51 at application loading time, e.g. accepting, rejecting, starting or inhibiting executable software based on integrity or source reliability
• CPC Class Codes: G06F 21/53 by executing in a restricted environment, e.g. sandbox or secure virtual machine
• CPC Class Codes: G06F 21/78 to assure secure storage of data address-based protection against unauthorised use of memory G06F12/14; record carriers for use with machines and with at least a part designed to carry digital markings G06K19/00

Abstract

A system that uses segmentation to safely execute native code. This system includes a processing element that executes the native code and a memory which stores code and data for the processing element. The processing element includes a segmentation mechanism which limits the native code executing on the processing element to accessing a specified segment of memory. The processing element also includes an instruction-processing unit, which is configured to execute a user-level instruction that causes the segmentation mechanism to limit memory accesses by the native code to the specified segment of the memory.

Claims

1. A computing device that uses segmentation to safely execute native code, comprising:

a processing element that executes the native code; and

a memory configured to store code and data for the processing element;

a segmentation mechanism within the processing element which limits the native code executing on the processing element to accessing a specified segment of memory;

an instruction-processing unit within the processing element, wherein the instruction-processing unit is configured to execute a user-level instruction that causes the segmentation mechanism to limit memory accesses by the native code to the specified segment of the memory;

a descriptor table in the memory that comprises memory segment descriptors that define one or more segments in the memory, wherein upon executing the user-level instruction, the instruction-processing unit accesses the descriptor table; and

a secure runtime environment that enforces code integrity, control flow integrity, and data integrity for native code executing on the processing element, wherein the secure runtime environment is configured to limit the ability of native code to access the user-level segmentation mechanism and to use the user-level segmentation mechanism to enforce control flow and data integrity for the native code module.

2. The computing device of claim 1, wherein the segmentation mechanism includes one or more of the following:

a register that contains the address of the descriptor table; and

one or more registers containing data from the descriptor table that describes a specified segment presently being accessed by the native code module.

3. The computing device of claim 1,

wherein the processing element includes an enable bit that enables the user-level segmentation mechanism to be configured;

and

wherein the processing element includes a status bit that indicates whether the user-level segmentation mechanism can be configured; and

wherein the secure runtime environment checks the status bit and if necessary unsets the enable bit to ensure that native code cannot configure the user-level segmentation mechanism.

4. The computing device of claim 1, wherein the secure runtime environment includes a validation mechanism configured to validate that the native code does not include instructions which configure the user-level segmentation mechanism.

5. The computing device of claim 1, further comprising a web browser configured to download and execute native code on the processing element.

6. The computing device of claim 1, wherein the processing element includes a feature bit that indicates whether the processing element supports user-level memory segmentation.

7. A method for using segmentation to safely execute native code, comprising:

receiving native code to be executed on a processing element;

executing a user-level instruction which configures a user-level segmentation mechanism in the processing element to limit the native code to accessing a specified memory segment, wherein executing the user-level instruction involves accessing a descriptor table in a memory that comprises memory segment descriptors that define one or more segments in the memory; and

executing the received native code received on the processing element;

wherein receiving the native code involves loading the native code into a secure runtime environment which enforces code integrity, control flow integrity, and data integrity for the native code, wherein the secure runtime environment limits the ability of the native code to access the user-level segmentation mechanism, and wherein executing the user-level instruction involves executing the user-level instruction through the secure runtime environment.

8. The method of claim 7, wherein executing the user-level instruction involves accessing one or more of the following:

a register that contains the address of the descriptor table; and

one or more registers containing data from the descriptor table that describes a memory segment presently being accessed by the native code module.

9. The method of claim 7,

wherein the processing element includes an enable bit that enables the user-level segmentation mechanism to be configured;

wherein the processing element includes a status bit that indicates whether the user-level segmentation mechanism can be configured; and

wherein the method further comprises checking the status bit, and if necessary unsetting the enable bit, to ensure that the native code module cannot configure the user-level segmentation mechanism.

10. The method of claim 7, wherein the method further comprises validating that the native code module does not include instructions which can configure the user-level segmentation mechanism.

11. The method of claim 7, wherein receiving the native code involves receiving the native code from a web browser which downloaded the native code from a remote website.

12. A non-transitory computer-readable storage medium storing instructions that when executed by a computing device cause the computing device to perform a method for using segmentation to safely execute native code, comprising:

receiving native code to be executed on a processing element;

executing a user-level instruction which configures a user-level segmentation mechanism in the processing element to limit the native code to accessing a specified memory segment, wherein executing the user-level instruction involves accessing a descriptor table in a memory that comprises memory segment descriptors that define one or more segments in the memory; and

executing the received native code received on the processing element;

wherein receiving the native code involves loading the native code into a secure runtime environment which enforces code integrity, control flow integrity, and data integrity for the native code, wherein the secure runtime environment limits the ability of the native code to access the user-level segmentation mechanism, and wherein executing the user-level instruction involves executing the user-level instruction through the secure runtime environment.

13. The computer-readable storage medium of claim 12, wherein executing the user-level instruction involves accessing one or more of the following:

a register that contains the address of the descriptor table; and

one or more registers containing data from the descriptor table that describes a memory segment presently being accessed by the native code module.

14. The computer-readable storage medium of claim 12,

wherein the processing element includes an enable bit that enables the user-level segmentation mechanism to be configured;

wherein the processing element includes a status bit that indicates whether the user-level segmentation mechanism can be configured; and

wherein the computer-readable storage medium further comprises checking the status bit, and if necessary unsetting the enable bit, to ensure that the native code module cannot configure the user-level segmentation mechanism.

15. The computer-readable storage medium of claim 12, wherein the method further comprises validating that the native code module does not include instructions which can configure the user-level segmentation mechanism.

16. The computer-readable storage medium of claim 12, wherein receiving the native code involves receiving the native code from a web browser which downloaded the native code from a remote website.

17. The computer-readable storage medium of claim 12, wherein the processing element includes a feature bit that indicates whether the processing element supports user-level memory segmentation.