CVE-2022-41724

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2023-02-28. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

Large handshake records may cause panics in crypto/tls. Both clients and servers may send large TLS handshake records which cause servers and clients, respectively, to panic when attempting to construct responses. This affects all TLS 1.3 clients, TLS 1.2 clients which explicitly enable session resumption (by setting Config.ClientSessionCache to a non-nil value), and TLS 1.3 servers which request client certificates (by setting Config.ClientAuth >= RequestClientCert).

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
62.1%
KEV
Not listed

Published

February 28, 2023

Last Modified

November 21, 2024

References (10)

Vendor Advisories for CVE-2022-41724(20)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(30)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatamq7/amq-broker-rhel8-operator-bundle:7.12.0-102024-05-21redhat
redhatkubevirt-0:4.14.1-2150.el82023-12-06redhat
redhatcontainer-tools:rhel8-8090020230825121312.e7857ab12023-11-14redhat
redhatcontainer-tools:4.0-8090020230828093056.e7857ab12023-11-14redhat
redhatcontainer-native-virtualization/vm-network-latency-checkup-rhel9:v4.14.0-242023-11-08redhat
redhatcontainernetworking-plugins-1:1.3.0-4.el92023-11-07redhat
redhatbuildah-1:1.31.3-1.el92023-11-07redhat
redhatpodman-2:4.6.1-5.el92023-11-07redhat
redhatrunc-4:1.1.9-1.el92023-11-07redhat
redhatskopeo-2:1.13.3-1.el92023-11-07redhat
redhatmigration-toolkit-virtualization/mtv-controller-rhel9:2.4.3-52023-10-25redhat
redhatcollectd-libpod-stats-0:1.0.4-5.el8ost2023-10-20redhat
redhatstf/smart-gateway-rhel8-operator:5.0.1-92023-10-20redhat
redhatrhosp-rhel8/osp-director-operator-bundle:1.3.0-192023-10-19redhat
redhatmta/mta-hub-rhel9:6.2.0-162023-08-14redhat
redhatjetstack-cert-manager-container-v1.10.2-182023-08-08redhat
redhatopenshift-clients-0:4.12.0-202307200611.p0.g49844f7.assembly.stream.el82023-08-03redhat
redhatskupper-cli-0:1.4.1-2.el92023-07-10redhat
redhatskopeo-2:1.11.2-2.1.rhaos4.13.el92023-06-23redhat
redhatodf4/mcg-rhel9-operator:v4.13.0-412023-06-21redhat
redhatopenshift-0:4.13.0-202305301919.p0.g0001a21.assembly.stream.el82023-06-07redhat
redhatopenshift-serverless-clients-0:1.8.1-3.el82023-06-05redhat
redhatetcd-0:3.3.23-14.el8ost2023-06-05redhat
redhatopenshift-serverless-1-tech-preview/logic-data-index-ephemeral-rhel8:1.29.0-12023-06-05redhat
redhatcri-o-0:1.26.3-6.rhaos4.13.gitb3475fb.el82023-05-30redhat
redhatopenshift-secondary-scheduler-operator/secondary-scheduler-operator-rhel8:v1.1-262023-05-18redhat
redhatmicroshift-0:4.13.0-202305161335.p0.g17cae44.assembly.4.13.0.el92023-05-18redhat
redhatopenshift-clients-0:4.13.0-202303241616.p0.g92b1a3d.assembly.stream.el82023-05-18redhat
redhatcryostat-tech-preview/jfr-datasource-rhel8:2.3.0-52023-05-18redhat
redhatopenshift4/ovirt-csi-driver-rhel8-operator:v4.13.0-202304190216.p0.g3e49f77.assembly.stream2023-05-17redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
stdlib—1.20.1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(16)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 43× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:25 UTCEPSS rescore
  2. 2026-07-11 08:25 UTCEPSS rescore
  3. 2026-07-09 19:08 UTCEPSS rescore
  4. 2026-07-08 15:12 UTCEPSS rescore
  5. 2026-07-07 13:44 UTCEPSS rescore
  6. 2026-07-06 16:25 UTCEPSS rescore
  7. 2026-07-06 02:21 UTCEPSS rescore
  8. 2026-07-05 02:28 UTCEPSS rescore
  9. 2026-07-04 06:29 UTCEPSS rescore
  10. 2026-07-02 16:58 UTCEPSS rescore
  11. 2026-07-01 15:04 UTCEPSS rescore
  12. 2026-06-30 23:20 UTCEPSS rescore
  13. 2026-06-30 23:20 UTCEPSS rescore
  14. 2026-06-29 14:04 UTCEPSS rescore
  15. 2026-06-29 14:04 UTCEPSS rescore
  16. 2026-06-28 14:06 UTCEPSS rescore
  17. 2026-06-28 04:54 UTCEPSS rescore
  18. 2026-06-28 04:54 UTCEPSS rescore
  19. 2026-06-28 04:34 UTCOSV refresh
  20. 2026-06-27 03:07 UTCEPSS rescore
  21. 2026-06-27 03:07 UTCEPSS rescore
  22. 2026-06-25 13:48 UTCEPSS rescore
  23. 2026-06-25 13:48 UTCEPSS rescore
  24. 2026-06-24 14:03 UTCEPSS rescore
  25. 2026-06-23 21:31 UTCEPSS rescore
Show 55 more
  1. 2026-06-23 21:31 UTCEPSS rescore
  2. 2026-06-22 14:24 UTCEPSS rescore
  3. 2026-06-21 14:55 UTCEPSS rescore
  4. 2026-06-21 14:55 UTCEPSS rescore
  5. 2026-06-21 01:58 UTCEPSS rescore
  6. 2026-06-21 01:58 UTCEPSS rescore
  7. 2026-06-19 19:24 UTCEPSS rescore
  8. 2026-06-19 19:24 UTCEPSS rescore
  9. 2026-06-18 17:51 UTCEPSS rescore
  10. 2026-06-18 17:51 UTCEPSS rescore
  11. 2026-06-17 17:51 UTCEPSS rescore
  12. 2026-06-17 17:51 UTCEPSS rescore
  13. 2026-06-16 17:51 UTCEPSS rescore
  14. 2026-06-15 17:46 UTCEPSS rescore
  15. 2026-06-14 23:16 UTCEPSS rescore
  16. 2026-06-13 22:59 UTCEPSS rescore
  17. 2026-06-12 23:10 UTCEPSS rescore
  18. 2026-06-12 23:10 UTCEPSS rescore
  19. 2026-06-11 13:58 UTCEPSS rescore
  20. 2026-06-11 13:58 UTCEPSS rescore
  21. 2026-06-10 22:17 UTCEPSS rescore
  22. 2026-06-10 15:17 UTCOSV refresh
  23. 2026-06-10 13:21 UTCEPSS rescore
  24. 2026-06-10 13:21 UTCEPSS rescore
  25. 2026-06-08 14:15 UTCEPSS rescore
  26. 2026-06-07 15:23 UTCEPSS rescore
  27. 2026-06-07 15:23 UTCEPSS rescore
  28. 2026-06-06 13:46 UTCEPSS rescore
  29. 2026-06-06 13:46 UTCEPSS rescore
  30. 2026-06-06 13:46 UTCEPSS rescore
  31. 2026-06-05 22:46 UTCEPSS rescore
  32. 2026-06-05 22:46 UTCEPSS rescore
  33. 2026-06-04 13:11 UTCEPSS rescore
  34. 2026-06-02 20:12 UTCEPSS rescore
  35. 2026-06-02 20:11 UTCEPSS rescore
  36. 2026-06-01 13:50 UTCEPSS rescore
  37. 2026-06-01 13:50 UTCEPSS rescore
  38. 2026-05-31 22:29 UTCEPSS rescore
  39. 2026-05-31 22:29 UTCEPSS rescore
  40. 2026-05-31 00:15 UTCEPSS rescore
  41. 2026-05-31 00:15 UTCEPSS rescore
  42. 2026-05-29 13:43 UTCEPSS rescore
  43. 2026-05-28 13:43 UTCEPSS rescore
  44. 2026-05-28 13:43 UTCEPSS rescore
  45. 2026-05-27 13:39 UTCEPSS rescore
  46. 2026-05-27 13:39 UTCEPSS rescore
  47. 2026-05-26 13:43 UTCEPSS rescore
  48. 2026-05-26 13:43 UTCEPSS rescore
  49. 2026-05-26 13:43 UTCEPSS rescore
  50. 2026-05-26 07:17 UTCEPSS rescore
  51. 2026-05-26 07:17 UTCEPSS rescore
  52. 2026-05-26 07:17 UTCEPSS rescore
  53. 2026-05-25 06:00 UTCEG score recompute
  54. 2026-05-25 06:00 UTCVendor advisory
  55. 2026-05-25 06:00 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2022-41724?
CVE-2022-41724 is a high vulnerability published on February 28, 2023. Large handshake records may cause panics in crypto/tls. Both clients and servers may send large TLS handshake records which cause servers and clients, respectively, to panic when attempting to construct responses. This affects all TLS 1.3 clients, TLS 1.2 clients which explicitly enable session…
When was CVE-2022-41724 disclosed?
CVE-2022-41724 was first published in the National Vulnerability Database on February 28, 2023, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-41724 actively exploited?
CVE-2022-41724 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 62.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2022-41724?
CVE-2022-41724 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2022-41724?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-41724, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-41724

Explore →

Is Your Infrastructure Affected by CVE-2022-41724?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs