RUSTSEC-2023-0013

Source
https://rustsec.org/advisories/RUSTSEC-2023-0013
Import Source
https://github.com/rustsec/advisory-db/blob/osv/crates/RUSTSEC-2023-0013.json
JSON Data
https://api.osv.dev/v1/vulns/RUSTSEC-2023-0013
Aliases
Published
2023-02-07T12:00:00Z
Modified
2023-11-08T04:11:08.219502Z
Summary
`NULL` dereference during PKCS7 data verification
Details

A NULL pointer can be dereferenced when signatures are being verified on PKCS7 signed or signedAndEnveloped data. In case the hash algorithm used for the signature is known to the OpenSSL library but the implementation of the hash algorithm is not available the digest initialization will fail. There is a missing check for the return value from the initialization function which later leads to invalid usage of the digest API most likely leading to a crash.

The unavailability of an algorithm can be caused by using FIPS enabled configuration of providers or more commonly by not loading the legacy provider.

PKCS7 data is processed by the SMIME library calls and also by the time stamp (TS) library calls. The TLS implementation in OpenSSL does not call these functions however third party applications would be affected if they call these functions to verify signatures on untrusted data.

Database specific
{
    "license": "CC0-1.0"
}
References

Affected packages

crates.io / openssl-src

Package

Affected ranges

Type
SEMVER
Events
Introduced
300.0.0
Fixed
300.0.12

Ecosystem specific

{
    "affected_functions": null,
    "affects": {
        "os": [],
        "functions": [],
        "arch": []
    }
}

Database specific

{
    "cvss": null,
    "informational": null,
    "categories": [
        "denial-of-service"
    ]
}