Advisory

GHSA-mfm6-r9g2-q4r7

Also known as: CVE-2022-1343, RUSTSEC-2022-0027

Summary

OCSP_basic_verify may incorrectly verify the response signing certificate

Details

The function OCSP_basic_verify verifies the signer certificate on an OCSP response. In the case where the (non-default) flag OCSP_NOCHECKS is used then the response will be positive (meaning a successful verification) even in the case where the response signing certificate fails to verify. It is anticipated that most users of OCSP_basic_verify will not use the OCSP_NOCHECKS flag. In this case the OCSP_basic_verify function will return a negative value (indicating a fatal error) in the case of a certificate verification failure. The normal expected return value in this case would be 0. This issue also impacts the command line OpenSSL "ocsp" application. When verifying an ocsp response with the "-no_cert_checks" option the command line application will report that the verification is successful even though it has in fact failed. In this case the incorrect successful response will also be accompanied by error messages showing the failure and contradicting the apparently successful result. Fixed in OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2).

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2022-05-04 00:00 UTC
Modified
2026-09-10 03:49 UTC

Affected packages and fixes

openssl-src

crates.io · All systems

Affected

  • introduced 300.0.0, fixed 300.0.6 (semver)

Fixed versions

300.0.6

Fix

  • Fixed version 300.0.6
    cargo update -p openssl-src --precise 300.0.6

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: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences