1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
//! BEMemory.h
//!
//! Refer GCC's documentation on `__asm__`:
//! <https://gcc.gnu.org/onlinedocs/gcc-4.7.2/gcc/Extended-Asm.html>
//!
//! And to LLVM's assembly documentation:
//! <https://llvm.org/docs/LangRef.html#inline-assembler-expressions>
//!
//! And of course Rust's own `asm!` macro documentation:
//! <https://doc.rust-lang.org/reference/inline-assembly.html>.
//! <https://doc.rust-lang.org/rust-by-example/unsafe/asm.html>
use asm;
use c_int;
/// Returns `true` iff the inlinable version of the jit_write_protect API is available.
/// These functions that can toggle JIT R^X permissions, while enforcing
/// control flow integrity using PAC. This function is intended to be used
/// only in performance-critical sections of code. Please consult
/// [the documentation] extensively before relying on this API.
///
/// This function should always be inlined. It will sign the return lr pointer
/// as a witness using PAC, and then call into the implementation.
///
/// The direct implementation is not permitted to be inlined into app binaries
/// because the instruction sequence required may change in the future.
///
/// Instead, we use a custom calling convention. This serves two purposes:
/// 1) Performance. The effects of this call can be precisely modeled, so
/// the performance is as close as possible to the case where we can
/// inline this body directly.
/// 2) Security. This calling convention greatly reduces the chances of spilling
/// an important value to the stack. See below.
///
/// In support of this function's security goals, users of this function must
/// confirm the following:
///
/// 1) You must not emit general PAC signing gadgets.
/// 2) The critical section defined by calls to these two functions must not
/// loop on any induction variable that is spilled to the stack, or otherwise
/// spill any important values there. An attacker can control these values.
/// If any values must be spilled or loaded from the heap or stack, they should be signed
/// outside the critical section, and authenticated inside.
/// 3) Do not create a gadget that is overly general. For example, wrapping this
/// function inside a body like this is very bad:
///
/// ```c
/// NEVER_INLINE void myFunction() {
/// if (variableFromStackOrHeap)
/// be_memory_inline_jit_restrict_rwx_to_rx_with_witness();
/// else
/// be_memory_inline_jit_restrict_rwx_to_rw_with_witness();
/// }
/// ```
///
/// Each use of this function should be maximally inlined to reduce the power
/// that attackers gain by manipulating calls to it.
///
/// Please look at the WebKit source code for an example.
///
/// [the documentation]: https://developer.apple.com/documentation/browserenginekit/protecting-code-compiled-just-in-time?language=objc
pub extern "C"
/// See [`be_memory_inline_jit_restrict_rwx_to_rw_with_witness`].
pub extern "C"