GHSA-mfm6-r9g2-q4r7

Suggest an improvement
Source
https://github.com/advisories/GHSA-mfm6-r9g2-q4r7
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2022/05/GHSA-mfm6-r9g2-q4r7/GHSA-mfm6-r9g2-q4r7.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-mfm6-r9g2-q4r7
Aliases
Related
Published
2022-05-04T00:00:23Z
Modified
2023-11-08T04:07:47.512143Z
Severity
  • 5.3 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N CVSS Calculator
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 OCSPNOCHECKS 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 OCSPNOCHECKS 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 "-nocertchecks" 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).

Database specific
{
    "nvd_published_at": "2022-05-03T16:15:00Z",
    "cwe_ids": [
        "CWE-295"
    ],
    "severity": "MODERATE",
    "github_reviewed": true,
    "github_reviewed_at": "2022-06-17T00:05:49Z"
}
References

Affected packages

crates.io / openssl-src

Package

Affected ranges

Type
SEMVER
Events
Introduced
300.0.0
Fixed
300.0.6