RustApplication · Rust Lang
CVE-2018-1000622
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencerustdoc plugin loading uses an uncontrolled search path when --plugin is specified without --plugin-path, causing it to search standard system locations for the plugin executable. An attacker can place a malicious binary in a location rustdoc searches (e.g., current directory or PATH), achieving code execution as the user running rustdoc.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
RustApplication
>= 0.8, <= 1.27.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify rustdoc installationRun 'rustdoc --version' to confirm rustdoc is installed and retrieve its version numberAffected if Version falls within range >= 0.8 and <= 1.27.0
-
Check for plugin usage in build or documentation scriptsSearch project files, build scripts, CI configurations, and documentation generation commands for occurrences of the '--plugin' flagAffected if The --plugin flag is present without a corresponding --plugin-path argument pointing to a trusted directory
-
Inspect current working directoryExamine the current directory from which rustdoc is executed for any unexpected binary files that match potential plugin namesAffected if Untrusted or unknown executable files exist in the directory where rustdoc runs
-
Review PATH environment variableList all directories in the system PATH and check for any writable or user-controlled locations containing executable filesAffected if Any directory in PATH contains unexpected binaries that could be selected as a plugin by rustdoc's search behavior
-
Audit documentation generation automationReview any automated documentation pipelines (CI/CD, Makefiles, scripts) that invoke rustdoc to confirm whether --plugin-path is explicitly provided whenever --plugin is usedAffected if Automation passes --plugin without --plugin-path, relying on rustdoc's default search behavior
You are affected if rustdoc version is between 0.8 and 1.27.0 inclusive AND the --plugin flag is used without an explicit --plugin-path argument in any command or script that runs rustdoc.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to Rust 1.27.1 or later, or always explicitly specify --plugin-path to a trusted directory when using the --plugin flag.
Fix this in Rust
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000622 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-1000622 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data