mirror of
https://github.com/OMGeeky/advisory-db.git
synced 2026-01-06 11:39:45 +01:00
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.
35 lines
1.2 KiB
Markdown
35 lines
1.2 KiB
Markdown
```toml
|
|
[advisory]
|
|
id = "RUSTSEC-2019-0014"
|
|
package = "image"
|
|
aliases = ["CVE-2019-16138"]
|
|
date = "2019-08-21"
|
|
keywords = ["drop", "use-after-free"]
|
|
url = "https://github.com/image-rs/image/pull/985"
|
|
|
|
[affected.functions]
|
|
"image::hdr::HDRDecoder::read_image_transform" = ["< 0.21.3, >= 0.10.2"]
|
|
|
|
[versions]
|
|
patched = [">= 0.21.3"]
|
|
unaffected = ["< 0.10.2"]
|
|
```
|
|
|
|
# Flaw in interface may drop uninitialized instance of arbitrary types
|
|
|
|
Affected versions of this crate would call `Vec::set_len` on an uninitialized
|
|
vector with user-provided type parameter, in an interface of the HDR image
|
|
format decoder. They would then also call other code that could panic before
|
|
initializing all instances.
|
|
|
|
This could run Drop implementations on uninitialized types, equivalent to
|
|
use-after-free, and allow an attacker arbitrary code execution.
|
|
|
|
Two different fixes were applied. It is possible to conserve the interface by
|
|
ensuring proper initialization before calling `Vec::set_len`. Drop is no longer
|
|
called in case of panic, though.
|
|
|
|
Starting from version `0.22`, a breaking change to the interface requires
|
|
callers to pre-allocate the output buffer and pass a mutable slice instead,
|
|
avoiding all unsafe code.
|