Advisory

RUSTSEC-2023-0010

Also known as: CVE-2022-4450, GHSA-v5w6-wcm8-jm4q

Summary

Double free after calling PEM_read_bio_ex

Details

The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and
decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload data.
If the function succeeds then the "name_out", "header" and "data" arguments are
populated with pointers to buffers containing the relevant decoded data. The
caller is responsible for freeing those buffers. It is possible to construct a
PEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex()
will return a failure code but will populate the header argument with a pointer
to a buffer that has already been freed. If the caller also frees this buffer
then a double free will occur. This will most likely lead to a crash. This
could be exploited by an attacker who has the ability to supply malicious PEM
files for parsing to achieve a denial of service attack.

The functions PEM_read_bio() and PEM_read() are simple wrappers around
PEM_read_bio_ex() and therefore these functions are also directly affected.

These functions are also called indirectly by a number of other OpenSSL
functions including PEM_X509_INFO_read_bio_ex() and
SSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL internal
uses of these functions are not vulnerable because the caller does not free the
header argument if PEM_read_bio_ex() returns a failure code. These locations
include the PEM_read_bio_TYPE() functions as well as the decoders introduced in
OpenSSL 3.0.

Severity

Not rated by the source.

Dates

Published
2023-02-07 12:00 UTC
Modified
2023-11-08 04:10 UTC

Affected packages and fixes

openssl-src

crates.io · All systems

Affected

  • introduced 0.0.0-0, fixed 111.25.0, introduced 300.0.0, fixed 300.0.12 (semver)

Fixed versions

111.25.0, 300.0.12

Fix

  • Fixed version 111.25.0
    cargo update -p openssl-src --precise 111.25.0
  • Fixed version 300.0.12
    cargo update -p openssl-src --precise 300.0.12

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: RustSec Advisory Database · CC0-1.0

Sources & licences