Race Condition Affecting rust-toolset:rhel8/rust-src package, versions <0:1.58.1-1.module+el8.6.0+14021+586eff1a


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.09% (40th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL8-RUSTTOOLSET-4235033
  • published21 Jan 2022
  • disclosed20 Jan 2022

Introduced: 20 Jan 2022

CVE-2022-21658  (opens in a new tab)
CWE-363  (opens in a new tab)
CWE-367  (opens in a new tab)

How to fix?

Upgrade RHEL:8 rust-toolset:rhel8/rust-src to version 0:1.58.1-1.module+el8.6.0+14021+586eff1a or higher.
This issue was patched in RHSA-2022:1894.

NVD Description

Note: Versions mentioned in the description apply only to the upstream rust-toolset:rhel8/rust-src package and not the rust-toolset:rhel8/rust-src package as distributed by RHEL. See How to fix? for RHEL:8 relevant fixed versions and status.

Rust is a multi-paradigm, general-purpose programming language designed for performance and safety, especially safe concurrency. The Rust Security Response WG was notified that the std::fs::remove_dir_all standard library function is vulnerable a race condition enabling symlink following (CWE-363). An attacker could use this security issue to trick a privileged program into deleting files and directories the attacker couldn't otherwise access or delete. Rust 1.0.0 through Rust 1.58.0 is affected by this vulnerability with 1.58.1 containing a patch. Note that the following build targets don't have usable APIs to properly mitigate the attack, and are thus still vulnerable even with a patched toolchain: macOS before version 10.10 (Yosemite) and REDOX. We recommend everyone to update to Rust 1.58.1 as soon as possible, especially people developing programs expected to run in privileged contexts (including system daemons and setuid binaries), as those have the highest risk of being affected by this. Note that adding checks in your codebase before calling remove_dir_all will not mitigate the vulnerability, as they would also be vulnerable to race conditions like remove_dir_all itself. The existing mitigation is working as intended outside of race conditions.

References

CVSS Scores

version 3.1