Extremely large RSA keys in certificate chains can cause a client/server to expend significant CPU time verifying signatures. With fix, the size of RSA keys transmitted during handshakes is restricted to <= 8192 bits. Based on a survey of publicly trusted RSA keys, there are currently only three certificates in circulation with keys larger than this, and all three appear to be test certificates that are not actively deployed. It is possible there are larger keys in use in private PKIs, but we target the web PKI, so causing breakage here in the interests of increasing the default safety of users of crypto/tls seems reasonable.
Project Subscriptions
| Vendors | Products |
|---|---|
|
Golang
Subscribe
|
Go
Subscribe
|
|
Redhat
Subscribe
|
Ansible Automation Platform
Subscribe
Cert Manager
Subscribe
Cryostat
Subscribe
Enterprise Linux
Subscribe
Logging
Subscribe
Migration Toolkit Applications
Subscribe
Migration Toolkit Virtualization
Subscribe
Network Observ Optr
Subscribe
Openshift
Subscribe
Openshift Api Data Protection
Subscribe
Openshift Data Foundation
Subscribe
Openshift Distributed Tracing
Subscribe
Openshift Secondary Scheduler
Subscribe
Openshift Serverless
Subscribe
Openstack
Subscribe
Rhmt
Subscribe
Run Once Duration Override Operator
Subscribe
Serverless
Subscribe
Stf
Subscribe
|
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2023-32978 | Extremely large RSA keys in certificate chains can cause a client/server to expend significant CPU time verifying signatures. With fix, the size of RSA keys transmitted during handshakes is restricted to <= 8192 bits. Based on a survey of publicly trusted RSA keys, there are currently only three certificates in circulation with keys larger than this, and all three appear to be test certificates that are not actively deployed. It is possible there are larger keys in use in private PKIs, but we target the web PKI, so causing breakage here in the interests of increasing the default safety of users of crypto/tls seems reasonable. |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Tue, 17 Jun 2025 16:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Redhat stf
|
|
| CPEs | cpe:/a:redhat:stf:1.5::el8 | |
| Vendors & Products |
Redhat service Telemetry Framework
|
Redhat stf
|
Tue, 22 Oct 2024 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Sun, 08 Sep 2024 18:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Redhat openshift Distributed Tracing
|
|
| CPEs | cpe:/a:redhat:openshift_distributed_tracing:2.9::el8 | |
| Vendors & Products |
Redhat openshift Distributed Tracing
|
Mon, 19 Aug 2024 22:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | ||
| Vendors & Products |
Redhat openshift Distributed Tracing
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: Go
Published:
Updated: 2025-02-13T16:49:16.368Z
Reserved: 2023-04-05T19:36:35.043Z
Link: CVE-2023-29409
Updated: 2024-08-02T14:07:46.160Z
Status : Modified
Published: 2023-08-02T20:15:11.940
Modified: 2024-11-21T07:57:00.287
Link: CVE-2023-29409
OpenCVE Enrichment
No data.
Weaknesses
EUVD