Unvalidated certificate issuance via ACME identifier mismatch
Published Sep 14, 2022 · Updated Aug 3, 2024
Certificate validation bypass in Keyfactor PrimeKey EJBCA before 7.9.0 allows remote attackers to obtain certificates for unvalidated DNS names. The ACME finalize endpoint accepts a CSR containing additional dnsNames after challenges validate only the identifiers originally placed in the order. An attacker must complete validation for at least one ordered identifier, after which the extra CSR names are issued even when the certificate profile forbids CSR subject-DN override.
Summary
What happened
Certificate validation bypass in Keyfactor PrimeKey EJBCA before 7.9.0 allows remote attackers to obtain certificates for unvalidated DNS names. The ACME finalize endpoint accepts a CSR containing additional dnsNames after challenges validate only the identifiers originally placed in the order. An attacker must complete validation for at least one ordered identifier, after which the extra CSR names are issued even when the certificate profile forbids CSR subject-DN override.
The record
- CVE
- CVE-2022-34831
- Published
- Sep 14, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-295, T1649
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 14, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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