CVE-2017-1000430: Base64 Integer Overflow Vulnerability

CRITICAL
Advisory Identifier: GHSA-x67x-vg9m-65c3
Share
CVSS 9.8
CWE-119
Published
Advisory Summary

CVE-2017-1000430 is a CRITICAL (CVSS 9.8) integer overflow vulnerability (CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer) affecting Base64 libraries in the crates.io ecosystem. The issue involves integer overflow in base64. Remediation is available by upgrading affected packages to version 0.5.2.

CVE-2017-1000430 at a Glance

CVE Identifier CVE-2017-1000430
GHSA Identifier GHSA-x67x-vg9m-65c3
Severity CRITICAL
CVSS v3.1 Base Score 9.8
CWE Classification CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer
Affected Product Base64
Package Ecosystem crates.io
Published Date
Last Updated

Security Impact

CVSS: 9.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2017-1000430

To remediate this vulnerability, upgrade all affected Base64 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

base64 fixed: 0.5.2 
Upgrade base64 to 0.5.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for base64

How to Check if You Are Affected

To determine whether your application is affected by CVE-2017-1000430, inspect your project dependencies for Base64:

inspect dependencies for base64

Analyze the terminal output to locate any version of Base64 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.5.2), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer, where the product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. this may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data. In Base64, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

Affected versions of this crate suffered from an integer overflow bug when calculating the size of a buffer to use when encoding base64 using the `encode_config_buf` and `encode_config` functions. If the input string was large, this would cause a buffer to be allocated that was too small. Since this function writes to the buffer using unsafe code, it would allow an attacker to write beyond the buffer, causing memory corruption and possibly the execution of arbitrary code. This flaw was corrected by using checked arithmetic to calculate the size of the buffer.

CVE-2017-1000430 Affected Base64 Versions

1 component(s)
Fixed Versions:
0.5.2
Product / Package Ecosystem Affected Versions Fixed Version
base64
 crates.io
< 0.5.2
0.5.2

References

NVD — CVE-2017-1000430 NVD
https://nvd.nist.gov/vuln/detail/CVE-2017-1000430
Security Fix Commit FIX COMMIT
https://github.com/alicemaz/rust-base64/commit/24ead980daf11ba563e4fb2516187a56a71ad319
Base64 Source Repository REPOSITORY
https://github.com/alicemaz/rust-base64
rustsec.org/advisories/rustsec-... WEB
https://rustsec.org/advisories/RUSTSEC-2017-0004.html

Frequently Asked Questions

What is CVE-2017-1000430?
CVE-2017-1000430 is a security vulnerability in Base64 involving Integer overflow in base64 under CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer.
Which Base64 versions are affected?
Affected versions include releases prior to 0.5.2 across affected packages: base64.
What version fixes CVE-2017-1000430?
Upgrading to 0.5.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is base64 affected?
Yes, base64 is affected in releases prior to 0.5.2. Upgrade your dependency to 0.5.2 or later.
What is the CVSS score of CVE-2017-1000430?
CVE-2017-1000430 has a CVSS v3.1 base score of 9.8 (CRITICAL) with vector string CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2017-1000430?
CVE-2017-1000430 is classified under CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer (The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.).
How can I check crates.io dependencies for CVE-2017-1000430?
Run the dependency tree command: 'inspect dependencies for base64'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-x67x-vg9m-65c3",
  "modified" : "2021-08-19T17:02:46Z",
  "published" : "2021-08-25T20:55:27Z",
  "aliases" : [ "CVE-2017-1000430" ],
  "summary" : "Integer overflow in base64",
  "details" : "Affected versions of this crate suffered from an integer overflow bug when\ncalculating the size of a buffer to use when encoding base64 using the\n`encode_config_buf` and `encode_config` functions.  If the input string\nwas large, this would cause a buffer to be allocated that was too small.\nSince this function writes to the buffer using unsafe code, it would\nallow an attacker to write beyond the buffer, causing memory corruption\nand possibly the execution of arbitrary code.\n\nThis flaw was corrected by using checked arithmetic to calculate\nthe size of the buffer.\n",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "base64"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.5.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2017-1000430"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/alicemaz/rust-base64/commit/24ead980daf11ba563e4fb2516187a56a71ad319"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/alicemaz/rust-base64"
  }, {
    "type" : "WEB",
    "url" : "https://rustsec.org/advisories/RUSTSEC-2017-0004.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-119" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2021-08-19T17:02:46Z",
    "nvd_published_at" : null
  }
}