Categories
CVE-2018-1000622

Vulnerability in Rust Programming Language rustdoc (CVE-2018-1000622)

Summary

Vulnerability in Rust Programming Language rustdoc (CVE-2018-1000622). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1.27.1 or later.

Original description

The description as published by the source.

The Rust Programming Language rustdoc version Between 0.8 and 1.27.0 contains a CWE-427: Uncontrolled Search Path Element vulnerability in rustdoc plugins that can result in local code execution as a different user. This attack appear to be exploitable via using the --plugin flag without the --plugin-path flag. This vulnerability appears to have been fixed in 1.27.1.

Source: OSV.dev (Open Source Vulnerabilities) NVD OSV

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-2018-1000622 has been found in Rust Programming Language rustdoc.
Successful exploitation can lead to full system takeover.
What to do: upgrade Rust Programming Language rustdoc to 1.27.1 or later.
If unsure, ask your IT team or search "Rust Programming Language rustdoc CVE-2018-1000622" on the vendor's site.

CVE-2018-1000622 (Rust Programming Language rustdoc)
Attack vector: local / unauthenticated
Patched: 1.27.1 — apply immediately
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

A vulnerability (unclassified) exists in Rust Programming Language rustdoc.

📍 Affected scope

Check the vendor advisory for the affected versions of Rust Programming Language rustdoc.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1.27.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

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

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Rust Programming Language rustdoc を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch
    Upgrade Rust Programming Language rustdoc to 1.27.1

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

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

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

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

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