RUSTSEC-2019-0014

Flaw in interface may drop uninitialized instance of arbitrary types

Reported

August 21, 2019

Issued

October 1, 2020 (last modified: June 13, 2023)

Package

image (crates.io)

Type

Vulnerability

Keywords

#drop #use-after-free

Aliases

References

https://github.com/image-rs/image/pull/985

CVSS Score

9.8 CRITICAL

CVSS Details

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

CVSS Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Patched

>=0.21.3

Unaffected

<0.10.2

Affected Functions

Version

image::hdr::HDRDecoder::read_image_transform

<0.21.3, >=0.10.2

Description

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.

Advisory available under CC0-1.0 license.