Certificate-policy bypass via disabled verification flag
Published Mar 28, 2023 · Updated Feb 19, 2025
Improper certificate validation in OpenSSL 1.0.2, 1.1.1, 3.0, and 3.1 allows attackers to bypass configured X.509 policies. X509_VERIFY_PARAM_add0_policy() adds a policy but fails to set X509_V_FLAG_POLICY_CHECK, so verification accepts certificates with invalid or incorrect policies. Reachability requires an application to rely on that function's documented implicit activation; policy checking is disabled by default and is not commonly used.
Summary
What happened
Improper certificate validation in OpenSSL 1.0.2, 1.1.1, 3.0, and 3.1 allows attackers to bypass configured X.509 policies. X509_VERIFY_PARAM_add0_policy() adds a policy but fails to set X509_V_FLAG_POLICY_CHECK, so verification accepts certificates with invalid or incorrect policies. Reachability requires an application to rely on that function's documented implicit activation; policy checking is disabled by default and is not commonly used.
The record
- CVE
- CVE-2023-0466
- Published
- Mar 28, 2023
- Updated
- Feb 19, 2025
- Vendor
- OpenSSL Project
- Product
- OpenSSL
- Classifications
- CWE-295, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 28, 2023CVE publishedPublication date reported by the CVE source.
- Feb 19, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0.2 <1.0.2zh
- Affected versionversion=1.1.1 <1.1.1u
- Affected versionversion=3.0.0 <3.0.9
- Affected versionversion=3.1.0 <3.1.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo