Embracing Rust’s Immutable Variables for Enhanced Software Reliability

Introduction

Rust, a programming language celebrated for its emphasis on safety and concurrent programming, introduces a distinctive concept: immutable variables. Unlike conventional languages where variables can be freely reassigned, Rust’s default immutability may initially seem restrictive. However, this intentional design choice serves as a potent safety mechanism that fosters productivity and facilitates robust concurrent programming. In this article, we will delve into the significance of immutable variables in Rust and explore their pivotal role in preventing errors and ensuring code security.

The Value of Immutability

In Rust, every variable is immutable by default, a core principle that distinguishes it from other programming languages. While this characteristic might appear limiting, it delivers substantial benefits that contribute to Rust’s reputation as a reliable and secure language.

  1. Error Prevention and Predictability: Immutability eliminates the need to track changes in variable values, greatly reducing the likelihood of errors stemming from unintended modifications. Debugging sessions that entail tracing unexpected value alterations become a rarity with immutable variables.
  2. Facilitating Concurrency: Immutable variables are particularly advantageous in concurrent programming. Their unchangeable nature negates the possibility of race conditions arising from multiple threads attempting to modify a variable concurrently. This simplifies concurrent programming and minimizes the chance of elusive bugs.

Putting Theory into Practice

To illustrate the concept, consider the following code snippet:

fn main() {
    let x = 5;
    println!("The value of x is: {}", x);
    x = 1; // This line triggers a compilation error
    println!("The value of x is: {}", x);
}

Attempting to reassign the value of x after its initial assignment results in a compilation error. The error message explicitly communicates that modifying an immutable variable multiple times is prohibited.

Enabling Mutability

In Rust, transforming an immutable variable into a mutable one requires the explicit use of the mut keyword. Here’s an example:

fn main() {
    let mut x = 9;
    println!("The value of x is: {}", x);
    x = 4;
    println!("The value of x is: {}", x);
}

This code snippet successfully compiles and runs, demonstrating the utilization of a mutable variable.

Distinguishing Immutable Variables from Constants

Although the concept of immutable variables may draw parallels to constants in other programming languages, they possess distinctive characteristics. Constants, defined using the const keyword, represent values determined at compile time. In contrast, immutable variables obtain their values at runtime and maintain their unchangeable nature throughout their lifespan.

Conclusion

Rust’s incorporation of immutable variables resonates with its commitment to safety, error prevention, and robust concurrent programming. While transitioning from mutable variables may require an adjustment, recognizing the advantages of immutability is pivotal for harnessing Rust’s capabilities fully. Through averting errors and enabling more straightforward concurrent programming, immutable variables contribute to Rust’s status as a language that empowers developers to craft secure and dependable software solutions.

What is Rust?

Introduction

Rust is a programming language created in 2015 by a small team of people, and later adopted by Mozilla.

It is a compiled low-level language, which aims to be as fast as C or C++, while incorporating some features from high-level languages such as Go, Python, or JavaScript.

Rust has three main goals:

  • Performance
  • Safety
  • Productivity

Performance

Rust aims to achieve performance similar to C or C++.

Rust is statically typed, which means the data type of a variable is known at compile time. This allows the compiler to optimize the code further than if we didn’t know the types.

Rust does not use garbage collection (despite being a low-level programming language). Garbage collection is where the program attempts to reclaim memory from objects no longer in use by the program.

Unlike languages like Python and JavaScript, Rust avoids these abstractions to minimize issues, making it a preferred choice for low-level programming.

Safety

Rust is designed to be completely memory safe. This means that memory-related exploits aren’t possible in Rust, unless you explicitly specify unsafe Rust code.

The Microsoft Security Response Centre reports that 70% of all CVEs assigned are memory safety issues. Microsoft states:

“This means that if that software had been written in Rust, 70% of these security issues would most likely have been eliminated. And we’re not the only company to have reported such findings.”

Rust provides tools to wrap unsafe actions, enabling static enforcement of unsafe code by the Rust compiler.

The memory safety is guaranteed by the concept of ownership, governed by these rules:

  • Each value has a variable, called an owner.
  • There can only be one owner at a time.
  • When the owner goes out of scope, the value will be dropped.

Values can be moved or borrowed between variables, but no value can have more than one owner.

Consider an example in Python:z

squares = (val * val for val in range(100))
print(min(squares))
print(max(squares))

What we want is:

0
9801

But what we get is:

>>> print(min(squares))
0
>>> print(max(squares))
Traceback (most recent call last):
  File "", line 1, in 
ValueError: max() arg is an empty sequence

This is because min alters the variable squares. It’s strange, because we just wanted the minimum — not to alter the whole variable!

In Rust, the same code is:

fn main()
   let squares = (0..100).map(|val| val * val);
   println!("{:?}", squares.min());
   println!("{:?}", squares.max());
}

When we try to compile this, Rust tells us:

error[E0382]: use of moved value: `squares`
 --> ownership.rs:4:21
  |
3 |    println!("{:?}", squares.min());
  |                     ------- value moved here
4 |    println!("{:?}", squares.max());
  |                     ^^^^^^^ value used here after move
  |
  = note: move occurs because `squares` has type `std::iter::Map<std::ops::Range, [closure@ownership.rs:2:31: 2:40]>`, which does not implement the `Copy` trait

The important part here is that Python allows functions to alter variables they do not own, whereas Rust doesn’t.

Productivity

Rust’s third major goal is productivity, and it provides a rich set of tools to support developers.

Note: The below list is read as:

  • Tool

Explanation of the above tool.

Some of these tools include:

  • Cargo

Rust’s version of NPM or PyPi. Download packages others have created.

  • Clippy

Microsoft Clippy, but re-imagined for Rust to aid with development.

  • RustFmt

Automatically formats Rust code.

  • Cargo Test

A built-in testing application created by the Rust developers.

  • Cargo docs

Automatically generates documentation for your code using documentation comments (written in Markdown). This documentation is then sent to docs.rs upon publishing to Cargo. Moreover, examples in documentation are automatically tested for you, eliminating untested documentation examples.

  • Rust-Analyzer

Rust Analyzer is like an intelligent IDE. It clearly labels what’s wrong with your code, explains why it’s wrong, points out the exact characters causing errors, and often provides an “auto-fix” function that rectifies errors automatically.

  • The Rust Book & Docs

Rust offers a comprehensive book called The Book, which covers everything you need to know about Rust. Neatly divided into chapters, it’s easily searchable and available for free. Additionally, due to Rust’s documentation comments, most libraries you use will have extensive documentation online.

With these tools at your disposal, compiling a Rust program and encountering bugs is incredibly rare. The tooling and language usually catch issues long before you hit the compile button.

Conclusion

If you are seeking exceptional speed, memory safety, and enhanced productivity, Rust is the language you’ve been looking for.

As Pentesters, part of our job is to provide solutions to developers. While suggesting a low-level language like Rust to Python developers might seem unconventional initially, Rust offers robust support, even allowing calls from functions written in other languages through foreign function interfacing.

We can leverage Rust to rewrite security or performance-critical code that seamlessly integrates with our existing codebase.

Here’s an example of calling C code:

extern "C" {
    fn abs(input: i32) -> i32;
}

fn main() {
    unsafe {
        println!("C believes that the absolute value of -3 is: {}", abs(-3));
    }
}