Sign in Sign up
JA · EN · FR
SecPulse
← Back
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.

AI summary snake-internal / snake-material-v2

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`` without authentication.
📍 Affected scope
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 (7 steps)

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. 5
    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. 6
    Apply patch patch 
    Upgrade sudo-rs to 0.2.1

    ステージング環境で 0.2.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

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

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

Affected packages

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

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →