Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2023-42456 low CVSS 3.3

Path Traversal in sudo-rs (CVE-2023-42456)

Summary

Path traversal in sudo-rs (CVE-2023-42456). Risk of unauthorized operations or information disclosure. Exploitable via useradd. Mitigation: upgrade to 0.2.1 or later.

Original description

The description as published by the source.

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.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2023-42456 has been found in sudo-rs.
Attackers can target a specific entry point like useradd over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.3/10.
What to do: upgrade sudo-rs to 0.2.1 or later.
If unsure, ask your IT team or search "sudo-rs CVE-2023-42456" on the vendor's site.

CVE-2023-42456 (sudo-rs) — CWE-22 / CVSS v3 3.3
Attack vector: local
Attack surface: useradd
Patched: 0.2.1 — apply immediately
Workaround: The sudo -K and sudo -k commands can run, even if a user has no sudo access.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Path traversal (CWE-22) exists in sudo-rs. Attackers reach the vulnerable code path via useradd.

📍 Affected scope

Check the vendor advisory for the affected versions of sudo-rs. Attack surface: useradd.

🔥 Severity

Severity: Low (CVSS 3.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.2.1.

🛡️ Workaround

Workaround: The sudo -K and sudo -k commands can run, even if a user has no sudo access.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'sudo-rs' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'sudo-rs' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で sudo-rs を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    The `sudo -K` and `sudo -k` commands can run, even if a user has no sudo access.

    パッチが適用されるまでの応急処置として、The sudo -K and sudo -k commands can run, even if a user has no sudo access. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade sudo-rs to 0.2.1

    ステージング環境で 0.2.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

rust sudo-rs
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.2.1"}]}]
crates.io sudo-rs
[{"type":"SEMVER","events":[{"introduced":"0.0.0-0"},{"fixed":"0.2.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details