mirror of
https://github.com/OMGeeky/advisory-db.git
synced 2026-01-05 19:20:34 +01:00
This reverts commit 0a981e2b6f.
These now need to use the new `affected_paths` attribute, which has a
different (VersionReq-bucketed) format.
22 lines
941 B
TOML
22 lines
941 B
TOML
[advisory]
|
|
id = "RUSTSEC-2017-0004"
|
|
package = "base64"
|
|
date = "2017-05-03"
|
|
url = "https://github.com/alicemaz/rust-base64/commit/24ead980daf11ba563e4fb2516187a56a71ad319"
|
|
title = "Integer overflow leads to heap-based buffer overflow in encode_config_buf"
|
|
patched_versions = [">= 0.5.2"]
|
|
keywords = ["memory-corruption"]
|
|
aliases = ["CVE-2017-1000430"]
|
|
description = """
|
|
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.
|
|
"""
|