CVE-2017-1000430
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 · uneditedrust-base64 version <= 0.5.1 is vulnerable to a buffer overflow when calculating the size of a buffer to use when encoding base64 using the 'encode_config_buf' and 'encode_config' functions
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 confidencerust-base64 versions 0.5.1 and below contain a buffer overflow vulnerability in the encode_config_buf and encode_config functions. The vulnerability exists in the buffer size calculation logic during base64 encoding, allowing an attacker to trigger a buffer overflow condition potentially leading to memory corruption or code execution.
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<= 0.5.1CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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.
-
Locate rust-base64 dependencySearch your project files (Cargo.toml) for 'rust-base64' or 'base64' in the [dependencies] section. Also check Cargo.lock for the base64 crate entry.Affected if The crate is listed as a dependency with version 0.5.1 or lower.
-
Identify the exact versionIn Cargo.lock, find the [[package]] entry with name "base64" and read the version field (e.g., version = "0.5.1").Affected if The version listed is 0.5.1 or any version below it (such as 0.5.0, 0.4.0, etc.).
-
Find usage of vulnerable functionsSearch your source code files (.rs) for calls to 'encode_config_buf' or 'encode_config' functions from the base64 crate.Affected if These functions are actively called in your codebase.
-
Verify encoding configuration usageReview the function calls found and check what EncodeConfig or encode configuration options are being passed (such as STANDARD, URL_SAFE, etc.).Affected if Any encode_config or encode_config_buf call is present, as the vulnerability exists in the buffer size calculation for all encoding operations.
You are affected if rust-base64 version 0.5.1 or lower is listed as a dependency in your project and your code calls encode_config or encode_config_buf for base64 encoding operations.
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.
dbcve · scopedUpgrade rust-base64 to a version greater than 0.5.1. Update the dependency in Cargo.toml to use a patched version of the library.
rust-base64 version 0.5.2 or higher (or migrate to the modern 'base64' crate)
- Update your Cargo.toml file to specify rust-base64 version 0.5.2 or higher, or the modern 'base64' crate
- Run 'cargo update' to fetch the updated dependency
- Run 'cargo build' or 'cargo test' to verify the update works correctly
- Ensure no other dependencies pull in a vulnerable version of rust-base64 by running 'cargo tree' and checking for transitive dependencies
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1000430 — 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-2017-1000430 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