Large RSA keys can cause high CPU usage in crypto/tls
Noroxi assessment
Priority: Monitor (action score 21/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.6% (FIRST EPSS); higher than 75.4% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Go standard library crypto/tls 1.19.12, 1.20.7, 1.21.0-rc.4.
Low priority for now. Upgrade to Go standard library crypto/tls 1.19.12, 1.20.7, 1.21.0-rc.4 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- BDU:2023-06242
- ALSA-2023:5738
- ALSA-2023:7762
- ALSA-2023:7763
- ALSA-2023:7764
- ALSA-2023:7765
- ALSA-2023:7766
- ALSA-2024:0121
- GO-2023-1987
- openSUSE-SU-2024:13093-1
- openSUSE-SU-2024:13094-1
- RHSA-2023:5009
- RHSA-2023:5721
- RHSA-2023:5738
- RHSA-2023:5805
- RHSA-2023:5964
- RHSA-2023:5965
- RHSA-2023:5969
- RHSA-2023:6298
- RHSA-2023:6840
- Published
- Aug 2, 2023
- Updated
- Jun 17, 2026
- EPSS
- 1.6% · 75th percentile
- CWE
- CWE-400
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| golang | go | cpe:2.3:a:golang:go |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- golang gobefore 1.19.12
- golang go1.20.0 and later · before 1.20.7
- golang go1.21.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Go). Independent of NVD's CPE analysis and usually ahead of it.
Go standard library crypto/tls
- before 1.19.12affected · semver
- 1.20.0-0 and later · before 1.20.7affected · semver
- 1.21.0-0 and later · before 1.21.0-rc.4affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | aardvark-dns | before 2:1.0.1-38.module_el8.9.0+3627+db8ec155 | 2:1.0.1-38.module_el8.9.0+3627+db8ec155 |
| AlmaLinux:8 | buildah | before 1:1.24.6-7.module_el8.9.0+3627+db8ec155 | 1:1.24.6-7.module_el8.9.0+3627+db8ec155 |
| AlmaLinux:8 | buildah-tests | before 1:1.24.6-7.module_el8.9.0+3687+dcd7ef8f | 1:1.24.6-7.module_el8.9.0+3687+dcd7ef8f |
| AlmaLinux:8 | buildah-tests | before 1:1.24.6-7.module_el8.9.0+3627+db8ec155 | 1:1.24.6-7.module_el8.9.0+3627+db8ec155 |
| AlmaLinux:8 | cockpit-podman | before 46-1.module_el8.7.0+3344+5bcd850f | 46-1.module_el8.7.0+3344+5bcd850f |
| AlmaLinux:8 | conmon | before 2:2.1.4-2.module_el8.9.0+3687+dcd7ef8f | 2:2.1.4-2.module_el8.9.0+3687+dcd7ef8f |
| AlmaLinux:8 | conmon | before 2:2.1.4-2.module_el8.9.0+3627+db8ec155 | 2:2.1.4-2.module_el8.9.0+3627+db8ec155 |
| AlmaLinux:8 | container-selinux | before 2:2.205.0-3.module_el8.9.0+3627+db8ec155 | 2:2.205.0-3.module_el8.9.0+3627+db8ec155 |
| AlmaLinux:8 | containernetworking-plugins | before 1:1.1.1-6.module_el8.9.0+3711+04fcca5e | 1:1.1.1-6.module_el8.9.0+3711+04fcca5e |
| AlmaLinux:8 | containers-common | before 2:1-38.module_el8.9.0+3627+db8ec155 | 2:1-38.module_el8.9.0+3627+db8ec155 |
| AlmaLinux:8 | crit | before 3.15-3.module_el8.6.0+2877+8e437bf5 | 3.15-3.module_el8.6.0+2877+8e437bf5 |
| AlmaLinux:8 | crit | before 3.15-3.module_el8.6.0+3137+d33c3efb | 3.15-3.module_el8.6.0+3137+d33c3efb |
| AlmaLinux:8 | criu | before 3.15-3.module_el8.6.0+3137+d33c3efb | 3.15-3.module_el8.6.0+3137+d33c3efb |
| AlmaLinux:8 | criu | before 3.15-3.module_el8.6.0+2877+8e437bf5 | 3.15-3.module_el8.6.0+2877+8e437bf5 |
| AlmaLinux:8 | criu-devel | before 3.15-3.module_el8.6.0+2877+8e437bf5 | 3.15-3.module_el8.6.0+2877+8e437bf5 |
| AlmaLinux:8 | criu-devel | before 3.15-3.module_el8.6.0+3137+d33c3efb | 3.15-3.module_el8.6.0+3137+d33c3efb |
| AlmaLinux:8 | criu-libs | before 3.15-3.module_el8.6.0+2877+8e437bf5 | 3.15-3.module_el8.6.0+2877+8e437bf5 |
| AlmaLinux:8 | criu-libs | before 3.15-3.module_el8.6.0+3137+d33c3efb | 3.15-3.module_el8.6.0+3137+d33c3efb |
| AlmaLinux:8 | crun | before 1.8.7-1.module_el8.9.0+3683+33eb0feb | 1.8.7-1.module_el8.9.0+3683+33eb0feb |
| AlmaLinux:8 | fuse-overlayfs | before 1.9-2.module_el8.9.0+3627+db8ec155 | 1.9-2.module_el8.9.0+3627+db8ec155 |
| AlmaLinux:8 | libslirp | before 4.4.0-1.module_el8.6.0+2877+8e437bf5 | 4.4.0-1.module_el8.6.0+2877+8e437bf5 |
| AlmaLinux:8 | libslirp | before 4.4.0-1.module_el8.6.0+3137+d33c3efb | 4.4.0-1.module_el8.6.0+3137+d33c3efb |
| AlmaLinux:8 | libslirp-devel | before 4.4.0-1.module_el8.6.0+2877+8e437bf5 | 4.4.0-1.module_el8.6.0+2877+8e437bf5 |
| AlmaLinux:8 | libslirp-devel | before 4.4.0-1.module_el8.6.0+3137+d33c3efb | 4.4.0-1.module_el8.6.0+3137+d33c3efb |
+96
Same product
golang: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-7187The "go get" implementation in Go 1.9.4, when the -insecure command-line option is used, does not validate the import path (get/vcs.go only 54Plan
- CVE-2018-16873In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to remote code execution when executed with the -u flag and52Plan
- CVE-2021-38297Go before 1.16.9 and 1.17.x before 1.17.2 has a Buffer Overflow via large arguments in a function invocation from a WASM module, when GOARCH42Plan
Published before and after this one in the same product
- ← EarlierCVE-2023-29405Jun 8, 2023 · Improper sanitization of LDFLAGS with embedded spaces in go command with cgo in cmd/go40Plan
- ← EarlierCVE-2023-29406Jul 11, 2023 · Insufficient sanitization of Host header in net/http26Monitor
- Later →CVE-2023-39318Sep 8, 2023 · Improper handling of HTML-like comments in script contexts in html/template24Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go standard library crypto/tls | 1.19.12 | Vendor (CNA) |
| Go standard library crypto/tls | 1.20.7 | Vendor (CNA) |
| Go standard library crypto/tls | 1.21.0-rc.4 | Vendor (CNA) |
| almalinux:buildah | 1:1.31.3-2.el9_3 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:go-toolset | 1.19.13-1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:golang | 1.19.13-1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:golang-bin | 1.19.13-1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:golang-docs | 1.19.13-1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:golang-misc | 1.19.13-1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:golang-race | 1.19.13-1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:golang-src | 1.19.13-1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:golang-tests | 1.19.13-1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:runc | 4:1.1.9-2.el9_3 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:skopeo | 2:1.13.3-3.el9_3 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:skopeo-tests | 2:1.13.3-3.el9_3 · AlmaLinux:9 | Package registry (OSV) |
| Go:stdlib | 1.19.12 | Package registry (OSV) |
| Go:stdlib | 1.20.7 | Package registry (OSV) |
| Go:stdlib | 1.21.0-rc.4 | Package registry (OSV) |
| opensuse:go1.19 | 1.19.12-150000.1.40.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:go1.19-openssl | 1.19.13.1-150000.1.8.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:go1.20 | 1.20.7-150000.1.20.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:go1.20-openssl | 1.20.8.1-150000.1.11.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| red hat:buildah | 1:1.29.1-10.1.rhaos4.14.el8 · Red Hat:openshift:4.14::el8 | Package registry (OSV) |
| red hat:buildah-debuginfo | 1:1.29.1-10.1.rhaos4.14.el8 · Red Hat:openshift:4.14::el8 | Package registry (OSV) |
| red hat:buildah-debugsource | 1:1.29.1-10.1.rhaos4.14.el8 · Red Hat:openshift:4.14::el8 | Package registry (OSV) |
| red hat:buildah-tests | 1:1.29.1-10.1.rhaos4.14.el8 · Red Hat:openshift:4.14::el8 | Package registry (OSV) |
| red hat:buildah-tests-debuginfo | 1:1.29.1-10.1.rhaos4.14.el8 · Red Hat:openshift:4.14::el8 | Package registry (OSV) |
| red hat:butane | 0:0.19.0-1.1.rhaos4.14.el8 · Red Hat:openshift:4.14::el8 | Package registry (OSV) |
| red hat:butane-debuginfo | 0:0.19.0-1.1.rhaos4.14.el8 · Red Hat:openshift:4.14::el8 | Package registry (OSV) |
| red hat:butane-debugsource | 0:0.19.0-1.1.rhaos4.14.el8 · Red Hat:openshift:4.14::el8 | Package registry (OSV) |
+32
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:1 | 2023-08-21 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+18 d
- TodayOct 21, 2026+1176 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- low · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- Low
Weakness class (CWE)
CWE-400 · Uncontrolled Resource ConsumptionCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
nvd-primary
Root cause
Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.
The bug in code
The whole CWE-400 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
function expand(node) { return node.children.map(expand);}Fixed
const MAX_DEPTH = 32;function expand(node, depth = 0) { if (depth > MAX_DEPTH) throw new Error("too deep"); return node.children.map((c) => expand(c, depth + 1));}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.