Certificate trust-policy bypass via misfiled rejected use
Published May 22, 2025 · Updated May 22, 2025
Improper certificate validation in OpenSSL 3.5.0 allows local users to mark a rejected certificate purpose as trusted via x509 -addreject. In apps/x509.c, x509_main pushes the option's ASN.1 purpose object onto the trust stack instead of the reject stack. Only trusted-certificate-format users who invoke the command to add rejected uses are exposed, and the resulting certificate can be accepted for a purpose intended to be denied.
Summary
What happened
Improper certificate validation in OpenSSL 3.5.0 allows local users to mark a rejected certificate purpose as trusted via x509 -addreject. In apps/x509.c, x509_main pushes the option's ASN.1 purpose object onto the trust stack instead of the reject stack. Only trusted-certificate-format users who invoke the command to add rejected uses are exposed, and the resulting certificate can be accepted for a purpose intended to be denied.
The record
- CVE
- CVE-2025-4575
- Published
- May 22, 2025
- Updated
- May 22, 2025
- Vendor
- OpenSSL Project
- Product
- OpenSSL
- Classifications
- CWE-295
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- May 22, 2025CVE publishedPublication date reported by the CVE source.
- May 22, 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=3.5.0 <3.5.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Weakness, pattern, technique
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