CVE-2025-22865: ParsePKCS1PrivateKey panic with partial keys in crypto/x509
First published: Tue 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.
Credit: security@golang.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Golang Crypto |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
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.
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.
What software is affected by CVE-2025-22865?
CVE-2025-22865 affects the Go crypto/x509 library.
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.
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.
- agent/weakness
- agent/title
- agent/references
- agent/first-publish-date
- agent/type
- agent/description
- agent/author
- agent/source
- collector/nvd-api
- source/NVD
- agent/severity
- agent/event
- agent/softwarecombine
- agent/tags
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- collector/epss-latest
- source/FIRST
- agent/epss
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/go
- canonical/golang crypto