CVE-2025-22865: ParsePKCS1PrivateKey panic with partial keys in crypto/x509
Published Jan 28, 2025
·Updated
Using ParsePKCS1PrivateKey to parse a RSA key that is missing the CRT values would panic when verifying that the key is well formed.
Affected Software
1 affected component
go crypto/x509
Event History
Jan 28, 2025
CVE Published
via MITRE·01:03 AM
Data Sourced
via MITRE·01:03 AM
DescriptionWeakness
Data Sourced
via Red Hat·02:01 AM
DescriptionSeverityAffected Software
Data Sourced
via NVD·02:15 AM
DescriptionSeverity
Frequently Asked Questions
1
What is the severity of CVE-2025-22865?
CVE-2025-22865 is classified as a high severity vulnerability due to its potential to cause a panic when verifying RSA keys.
2
How do I fix CVE-2025-22865?
To fix CVE-2025-22865, ensure that RSA keys include the necessary CRT values before attempting to parse them with ParsePKCS1PrivateKey.
3
What software is affected by CVE-2025-22865?
CVE-2025-22865 affects the Go crypto/x509 library.
4
Can CVE-2025-22865 lead to denial of service?
Yes, CVE-2025-22865 can lead to denial of service as it may cause an application to panic.
5
Is CVE-2025-22865 a coding error or a design flaw?
CVE-2025-22865 is primarily a coding error related to the handling of RSA keys in the Go crypto/x509 library.