mirror of
https://github.com/OMGeeky/advisory-db.git
synced 2026-01-09 05:01:06 +01:00
ac125ee29a
As proposed in #240 and tracked in #414, this PR translates all advisories into the new "V3" advisory format, which is based on Markdown with leading TOML front matter. This format makes it easier to see rendered Markdown syntax descriptions, whether rendered by an IDE or GitHub. This should help with both crafting advisories initially as well as review, and ideally encourages more lengthy descriptions. Support for this format shipped in `cargo-audit` v0.12.0 on May 6th, 2020.
26 lines
928 B
Markdown
26 lines
928 B
Markdown
```toml
|
|
[advisory]
|
|
id = "RUSTSEC-2017-0004"
|
|
package = "base64"
|
|
aliases = ["CVE-2017-1000430"]
|
|
date = "2017-05-03"
|
|
keywords = ["memory-corruption"]
|
|
url = "https://github.com/alicemaz/rust-base64/commit/24ead980daf11ba563e4fb2516187a56a71ad319"
|
|
|
|
[versions]
|
|
patched = [">= 0.5.2"]
|
|
```
|
|
|
|
# Integer overflow leads to heap-based buffer overflow in encode_config_buf
|
|
|
|
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.
|