Email me

Rust advisories / sudo-rs

Vulnerability LowRUSTSEC-2023-0069 · sudo-rs

RUSTSEC-2023-0069: sudo-rs: Path Traversal vulnerability

Short answerA security vulnerability in the sudo-rs crate: sudo-rs: Path Traversal vulnerability. Low severity (CVSS 3.1). Fixed in 0.2.1: update to a fixed version.

Cratesudo-rs
TypeVulnerability (file-disclosure)
Affected versionsBefore 0.2.1.
Fixed in0.2.1
SeverityLow, CVSS 3.1
CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:N/I:L/A:L
Published2023-11-01
Last changed2026-10-13
Also known asCVE-2023-42456, GHSA-2r3c-m6v7-9354

What to do

  1. See which version you have: cargo tree -i sudo-rs (it also shows which of your dependencies pulls it in).
  2. Update within your version requirement: cargo update -p sudo-rs. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for example sudo-rs = "0.2.1") or update the dependency that pulls it in.
  3. Check again with cargo audit, or paste your Cargo.lock into our Cargo.toml checker.

Details from the advisory

Impact

An issue was discovered where usernames containing the . and / characters could result in the corruption of specific files on the filesystem. As usernames are generally not limited by the characters they can contain, a username appearing to be a relative path can be constructed. For example we could add a user to the system containing the username ../../../../bin/cp. When logged in as a user with that name, that user could run sudo -K to clear their session record file. The session code then constructs the path to the session file by concatenating the username to the session file storage directory, resulting in a resolved path of /bin/cp. The code then clears that file, resulting in the cp binary effectively being removed from the system.

An attacker needs to be able to login as a user with a constructed username. Given that such a username is unlikely to exist on an existing system, they will also need to be able to create the users with the constructed usernames.

Patches

The bug is fixed in version 0.2.1 of sudo-rs. Sudo-rs now uses the uid for the user instead of their username for determining the filename. Note that an upgrade to this version will result in existing session files being ignored and users will be forced to re-authenticate. It also fully eliminates any possibility of path traversal, given that uids are always integer values.

The issue was corrected in commit bfdbda22968e3de43fa8246cab1681cfd5d5493d.

References

From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.

Other advisories for sudo-rs

Full security history of sudo-rs

Up next

Same cratesudo-rs: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →

Did this answer your question?

Get the receipts by email.

What my AI agents tried this week, with the real numbers: what worked, what flopped, what made money. One email when there is something worth reading.

No spam, never sold. Every email has a one-click unsubscribe.

Popular in the shop

All 124 tools →

Browse: Bundles and kitsHome, family and schoolMoney and businessAI toolsSports and fitnessMaking and hobbiesFood and drinkIndie dev and launchTrading and quant

Free: Landing page teardown iPhone app cost calculator LLM API cost calculator Paid online: $49 Launch Check App builds Articles FAQ