Add exploit mitigations chapter to the rustc book #76858

rcvalle · 2020-09-18T01:09:32Z

This section documents the exploit mitigations applicable to the Rust compiler when building programs for the Linux operating system on the AMD64 architecture and equivalent. This was done for a project I'm currently working on, and I hope it'll also be helpful to others.

rust-highfive · 2020-09-18T01:09:35Z

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @steveklabnik (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

src/doc/rustc/src/exploit-mitigations.md

tesuji · 2020-09-18T02:19:23Z

src/doc/rustc/src/exploit-mitigations.md

+The Rust compiler supports stack clashing protection via stack probing, and
+enables it by default since version 1.20.0 (2017-08-31)[26]–[29].
+
+![Screenshot listing cross references to __rust_probestack in hello-rust.](images/image1.png "Cross references to __rust_probestack in hello-rust.")


Can we use posix tools output like objdump, readelf instead of ghidra or ida screenshot ?

I don't know of any common Linux tool that can list cross references to addresses/symbols. I could perhaps use Radare2, but it also isn't a common Linux tool, and it would be the same as using Ghidra or IDA Pro.

I agree there is no such a general CLI tool could do that.
Could you list the toolname in the image description ?
Or have a small section about tools used.

tesuji · 2020-09-18T02:20:53Z

src/doc/rustc/src/exploit-mitigations.md

+The Rust compiler supports integer overflow checks, and enables it when
+debug assertions are enabled since version 1.0.0 (2015-05-15)[14]–[17], but
+support for it was not completed until version 1.1.0 (2015-06-25)[16]. An
+option to control integer overflow checks was later stabilized in version
+1.17.0 (2017-04-27)[18]–[20].


Thanks for the history, but I don't think it is needed to including this.
We want to follow what current nightly do.

Yes, in general, all docs are written "in the present", and we don't include specific version numbers.

I can remove these. However, this entire document is written as a historical account of these exploit mitigations' major milestones for Rust, and removing these will make this part inconsistent with the rest of the document. Let me know if you still prefer I remove these.

Yes, we don't write docs in that style. That doesn't mean it's not useful to have, it's just not the way that the documentation is organized.

src/doc/rustc/src/exploit-mitigations.md

tesuji · 2020-09-22T04:42:23Z

src/doc/rustc/src/exploit-mitigations.md

@@ -0,0 +1,583 @@
+# Exploit Mitigations
+


Do we need a target audience section ? Or it applies to everybody interested.

The original document was initially targeted at security and software engineers working on the project I'm currently working on, but later was opened to everyone interested. I think having it open to everyone interested would make sense here.

I can also add the following target audience and prior knowledge similarly to how it is in the original document:

This chapter describes exploit mitigations supported by the Rust compiler, and is by no means an extensive survey of the Rust programming language’s security features.

This chapter is for software engineers working with the Rust programming language, and assumes prior knowledge of the Rust programming language and its toolchain.

I removed it because I didn't see any other chapters containing a target audience and prior knowledge. What do you think?

tesuji · 2020-09-22T04:46:14Z

src/doc/rustc/src/exploit-mitigations.md

+The Rust compiler supports stack clashing protection via stack probing, and
+enables it by default since version 1.20.0 (2017-08-31)[26]–[29].
+
+![Screenshot listing cross references to __rust_probestack in hello-rust.](images/image1.png "Cross references to __rust_probestack in hello-rust.")


I agree there is no such a general CLI tool could do that.
Could you list the toolname in the image description ?
Or have a small section about tools used.

steveklabnik · 2020-10-14T14:59:24Z

I'd like someone from @rust-lang/compiler to approve this PR. I don't have any more feedback, but ultimately, this is about their part of the project, and it's a big addition.

Sorry for this taking so long, @rcvalle .

alex

I think this is a great survey of what exists... however I'm a bit concerned a reader might take teh wrong conclusions away from this. Specifically, the document doesn't really describe how effective any of these mitigations are, and indeed the history of C is a history of people claiming a mitigation will solve memory unsafety and then it failing to do so.

To address this, I'd suggest that the introduction flag this, rather than try to document how effective each mitigation is.

src/doc/rustc/src/exploit-mitigations.md

rcvalle · 2020-10-15T01:08:28Z

I'd like someone from @rust-lang/compiler to approve this PR. I don't have any more feedback, but ultimately, this is about their part of the project, and it's a big addition.

Sorry for this taking so long, @rcvalle .

Np at all. Thank you @steveklabnik and others for their time!

rcvalle · 2020-10-15T01:13:49Z

I think this is a great survey of what exists... however I'm a bit concerned a reader might take teh wrong conclusions away from this. Specifically, the document doesn't really describe how effective any of these mitigations are, and indeed the history of C is a history of people claiming a mitigation will solve memory unsafety and then it failing to do so.

To address this, I'd suggest that the introduction flag this, rather than try to document how effective each mitigation is.

What do you think about the following:

This document does not discuss the effectiveness of these exploit mitigations as they vary greatly depending on several factors besides their design and implementation, but rather describe what they do, so their effectiveness can be understood within a given context.

Which is why this document does not discuss the effectiveness of these exploit mitigations.

alex · 2020-10-15T01:17:32Z

Looks great, thanks!

…

On Wed, Oct 14, 2020 at 9:14 PM Ramon de C Valle ***@***.***> wrote: I think this is a great survey of what exists... however I'm a bit concerned a reader might take teh wrong conclusions away from this. Specifically, the document doesn't really describe how *effective* any of these mitigations are, and indeed the history of C is a history of people claiming a mitigation will solve memory unsafety and then it failing to do so. To address this, I'd suggest that the introduction flag this, rather than try to document how effective each mitigation is. What do you think about the following: This document does not discuss the effectiveness of these exploit mitigations as they vary greatly depending on several factors besides their design and implementation, but rather describe what they do, so their effectiveness can be understood within a given context. Which is why this document does not discuss the effectiveness of these exploit mitigations. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#76858 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAAGBEA4SMSQR7WLYWENULSKZEF3ANCNFSM4RRHLMZQ> .

-- All that is necessary for evil to succeed is for good people to do nothing.

jyn514

Is this waiting on anything? It looks good to me :)

src/doc/rustc/src/exploit-mitigations.md

Dylan-DPC-zz · 2020-11-01T14:40:31Z

waiting for another review from @steveklabnik after recent changes

steveklabnik

Sorry, I did not realize this was blocked on me!

steveklabnik · 2020-11-20T19:53:16Z

@bors: r+ rollup

bors · 2020-11-20T19:53:18Z

📌 Commit 9999616 has been approved by steveklabnik

…ns, r=steveklabnik Add exploit mitigations chapter to the rustc book This section documents the exploit mitigations applicable to the Rust compiler when building programs for the Linux operating system on the AMD64 architecture and equivalent. This was done for a project I'm currently working on, and I hope it'll also be helpful to others.

m-ou-se · 2020-11-21T10:56:45Z

This failed in #79252 on x86_64-apple: https://github.com/rust-lang-ci/rust/runs/1434709746

doc tests for: /Users/runner/work/rust/rust/src/doc/rustc/src/exploit-mitigations.md

running 3 tests
test /Users/runner/work/rust/rust/src/doc/rustc/src/exploit-mitigations.md - Exploit_Mitigations::Exploit_mitigations::Integer_overflow_checks (line 180) ... ok
test /Users/runner/work/rust/rust/src/doc/rustc/src/exploit-mitigations.md - Exploit_Mitigations::Exploit_mitigations::Stack_clashing_protection (line 280) ... ok
test /Users/runner/work/rust/rust/src/doc/rustc/src/exploit-mitigations.md - Exploit_Mitigations::Exploit_mitigations::Heap_corruption_protection (line 381) ... FAILED

failures:

---- /Users/runner/work/rust/rust/src/doc/rustc/src/exploit-mitigations.md - Exploit_Mitigations::Exploit_mitigations::Heap_corruption_protection (line 381) stdout ----
Test executable succeeded, but it's marked `should_panic`.

failures:
    /Users/runner/work/rust/rust/src/doc/rustc/src/exploit-mitigations.md - Exploit_Mitigations::Exploit_mitigations::Heap_corruption_protection (line 381)

@bors r-

jyn514 · 2020-11-24T03:09:36Z

@rcvalle do you mind squashing the commits a little? There are instructions at https://rustc-dev-guide.rust-lang.org/git.html#rebasing.

rcvalle · 2020-11-24T03:14:17Z

@rcvalle do you mind squashing the commits a little? There are instructions at https://rustc-dev-guide.rust-lang.org/git.html#rebasing.

Not at all. Do you prefer me to squash them all into a single commit?

jyn514 · 2020-11-24T03:16:04Z

However many you think makes sense - for a PR this big, I think up to 5 is fine. I just think changes like 'Remove deadwood from sentence' don't need to be their own commit, since they aren't particularly valuable for telling you why the code is a certain way.

This section documents the exploit mitigations applicable to the Rust compiler when building programs for the Linux operating system on the AMD64 architecture and equivalent.

rcvalle · 2020-11-24T03:31:14Z

However many you think makes sense - for a PR this big, I think up to 5 is fine. I just think changes like 'Remove deadwood from sentence' don't need to be their own commit, since they aren't particularly valuable for telling you why the code is a certain way.

I think most of them didn't need a separate commit, so I just squashed them all.

jyn514 · 2020-11-24T04:30:17Z

@bors r=steveklabnik rollup

bors · 2020-11-24T04:30:19Z

📌 Commit 5b1cb0e has been approved by steveklabnik

…as-schievink Rollup of 10 pull requests Successful merges: - rust-lang#76858 (Add exploit mitigations chapter to the rustc book) - rust-lang#79310 (Make `fold_item_recur` non-nullable) - rust-lang#79312 (Get rid of `doctree::Impl`) - rust-lang#79321 (Accept '!' in intra-doc links) - rust-lang#79346 (Allow using `-Z fewer-names=no` to retain value names) - rust-lang#79351 (Fix typo in `keyword` docs for traits) - rust-lang#79354 (BTreeMap: cut out the ceremony around BoxedNode) - rust-lang#79358 (BTreeMap/BTreeSet: make public doc more consistent) - rust-lang#79367 (Allow disabling TrapUnreachable via -Ztrap-unreachable=no) - rust-lang#79374 (Add note to use nightly when using expr in const generics) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup

rust-highfive assigned steveklabnik Sep 18, 2020

rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Sep 18, 2020

tesuji reviewed Sep 18, 2020

View reviewed changes

alex reviewed Sep 18, 2020

View reviewed changes

src/doc/rustc/src/exploit-mitigations.md Outdated Show resolved Hide resolved

marmeladema reviewed Sep 21, 2020

View reviewed changes

src/doc/rustc/src/exploit-mitigations.md Outdated Show resolved Hide resolved

tesuji reviewed Sep 22, 2020

View reviewed changes

alex reviewed Oct 14, 2020

View reviewed changes

src/doc/rustc/src/exploit-mitigations.md Outdated Show resolved Hide resolved

jyn514 added the A-docs Area: Documentation for any part of the project, including the compiler, standard library, and tools label Oct 30, 2020

camelid added the T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. label Oct 30, 2020

jyn514 approved these changes Oct 30, 2020

View reviewed changes

src/doc/rustc/src/exploit-mitigations.md Outdated Show resolved Hide resolved

crlf0710 added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Nov 20, 2020

steveklabnik approved these changes Nov 20, 2020

View reviewed changes

bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Nov 20, 2020

Dylan-DPC-zz mentioned this pull request Nov 21, 2020

Rollup of 9 pull requests #79252

Closed

bors added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Nov 21, 2020

Add exploit mitigations chapter to the rustc book

5b1cb0e

This section documents the exploit mitigations applicable to the Rust compiler when building programs for the Linux operating system on the AMD64 architecture and equivalent.

bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Nov 24, 2020

jonas-schievink mentioned this pull request Nov 24, 2020

Rollup of 10 pull requests #79377

Merged

bors merged commit 8fde4be into rust-lang:master Nov 24, 2020

rustbot added this to the 1.50.0 milestone Nov 24, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add exploit mitigations chapter to the rustc book #76858

Add exploit mitigations chapter to the rustc book #76858

rcvalle commented Sep 18, 2020 •

edited

Loading

rust-highfive commented Sep 18, 2020

tesuji Sep 18, 2020

rcvalle Sep 18, 2020

tesuji Sep 22, 2020

tesuji Sep 18, 2020

steveklabnik Sep 18, 2020

rcvalle Sep 18, 2020

steveklabnik Sep 21, 2020

tesuji Sep 22, 2020

rcvalle Sep 22, 2020

rcvalle Sep 24, 2020

tesuji Sep 22, 2020

steveklabnik commented Oct 14, 2020

alex left a comment

rcvalle commented Oct 15, 2020

rcvalle commented Oct 15, 2020

alex commented Oct 15, 2020 via email

jyn514 left a comment

Dylan-DPC-zz commented Nov 1, 2020

steveklabnik left a comment

steveklabnik commented Nov 20, 2020

bors commented Nov 20, 2020

m-ou-se commented Nov 21, 2020

jyn514 commented Nov 24, 2020

rcvalle commented Nov 24, 2020

jyn514 commented Nov 24, 2020

rcvalle commented Nov 24, 2020

jyn514 commented Nov 24, 2020

bors commented Nov 24, 2020

Add exploit mitigations chapter to the rustc book #76858

Add exploit mitigations chapter to the rustc book #76858

Conversation

rcvalle commented Sep 18, 2020 • edited Loading

rust-highfive commented Sep 18, 2020

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

steveklabnik commented Oct 14, 2020

alex left a comment

Choose a reason for hiding this comment

rcvalle commented Oct 15, 2020

rcvalle commented Oct 15, 2020

alex commented Oct 15, 2020 via email

jyn514 left a comment

Choose a reason for hiding this comment

Dylan-DPC-zz commented Nov 1, 2020

steveklabnik left a comment

Choose a reason for hiding this comment

steveklabnik commented Nov 20, 2020

bors commented Nov 20, 2020

m-ou-se commented Nov 21, 2020

jyn514 commented Nov 24, 2020

rcvalle commented Nov 24, 2020

jyn514 commented Nov 24, 2020

rcvalle commented Nov 24, 2020

jyn514 commented Nov 24, 2020

bors commented Nov 24, 2020

rcvalle commented Sep 18, 2020 •

edited

Loading