Application crash via crafted PKIX distinguished name
Published Feb 20, 2023 · Updated Nov 27, 2024
Resource exhaustion in Notary Project notation-go before 1.0.0-rc.3 allows attackers to crash verifying applications via crafted X.509 identities. ParseDistinguishedName sends distinguished names containing =# to an ASN.1 BER parser without first rejecting that unsupported form, causing excessive memory consumption. The path is reached when a trust-policy identity or leaf-certificate subject contains =# during signature verification, and memory exhaustion kills the hosting application.
Summary
What happened
Resource exhaustion in Notary Project notation-go before 1.0.0-rc.3 allows attackers to crash verifying applications via crafted X.509 identities. ParseDistinguishedName sends distinguished names containing =# to an ASN.1 BER parser without first rejecting that unsupported form, causing excessive memory consumption. The path is reached when a trust-policy identity or leaf-certificate subject contains =# during signature verification, and memory exhaustion kills the hosting application.
The record
- CVE
- CVE-2023-25656
- Published
- Feb 20, 2023
- Updated
- Nov 27, 2024
- Vendor
- Notary Project
- Product
- notation-go
- Classifications
- CWE-400, CWE-770, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 20, 2023CVE publishedPublication date reported by the CVE source.
- Nov 27, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0.0-rc.3 <1.0.0-rc.3
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.
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