# What is CVE-2022-3602? > CVE-2022-3602 is a high-severity flaw (CVSS 7.5) in OpenSSL, published on 1 November 2022. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 91%. If you run an affected version, plan in the vendor’s fix. Canonical page: https://www.precursorintelligence.com/what-is/cve-2022-3602 ## At a glance - **Verdict:** Fix this soon. Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month. - **Precursor Intelligence risk score:** 75 out of 100 (High); action: Patch now. Kept up to date as the evidence changes. - **Severity:** High (CVSS 7.5 out of 10) - **Known to be exploited:** No, not on the list of flaws known to be exploited today - **Chance of use in the next 30 days:** 91% (latest exploit-likelihood forecast) - **Published:** 1 November 2022 - **Record last updated:** 4 November 2025 - **Main product:** OpenSSL - **Affected products:** 4 ## What is CVE-2022-3602? In plain terms It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can take it offline. ### The official description A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to continue certificate verification despite failure to construct a path to a trusted issuer. An attacker can craft a malicious email address to overflow four attacker-controlled bytes on the stack. This buffer overflow could result in a crash (causing a denial of service) or potentially remote code execution. Many platforms implement stack overflow protections which would mitigate against the risk of remote code execution. The risk may be further mitigated based on stack layout for any given platform/compiler. Pre-announcements of CVE-2022-3602 described this issue as CRITICAL. Further analysis based on some of the mitigating factors described above have led this to be downgraded to HIGH. Users are still encouraged to upgrade to a new version as soon as possible. In a TLS client, this can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects. Fixed in OpenSSL 3.0.7 (Affected 3.0.0,3.0.1,3.0.2,3.0.3,3.0.4,3.0.5,3.0.6). ### What kind of flaw is it? - CWE-787: Out-of-bounds Write ### How an attack on it works - Where an attacker can be: Anywhere on the internet - How hard it is to pull off: Easy: no special conditions - Login needed first: No login needed - Does someone have to click: No, nobody has to do anything - What an attacker gets: Can take it offline Severity vector: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H` ## Is CVE-2022-3602 being exploited? Not that we know of It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 91%. That can change at any time, which is why we keep watching. Exploit likelihood over the last 7 days: 91%, 91%, 91%, 91%, 91%, 91%, 91%. ### Timeline - 1 November 2022: Published - 4 November 2025: Record last updated ### How Precursor Intelligence ranks it CVE-2022-3602 scores **75 out of 100 (High)**, with the action "Patch now". Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less: - Evidence it is being exploited: biggest factor - How severe it is: strong factor - How widely exposed it is: smaller factor - Threat activity around it: smaller factor 85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it. ## Who is affected by CVE-2022-3602? The published record lists 4 products. Versions are as published: "3.0.0 to before 3.0.7" means from 3.0.0 up to, but not including, 3.0.7. - [OpenSSL](https://www.precursorintelligence.com/product/openssl/openssl) by [OpenSSL](https://www.precursorintelligence.com/vendors/openssl) (Application): 3.0.0 to before 3.0.7 - [Fedora](https://www.precursorintelligence.com/product/fedoraproject/fedora) by [Fedoraproject](https://www.precursorintelligence.com/vendors/fedoraproject) (Operating system): 26, 27, 36, 37 - [Node.js](https://www.precursorintelligence.com/product/nodejs/node.js) by [Nodejs](https://www.precursorintelligence.com/vendors/nodejs) (Application): 18.0.0 to before 18.11.0, 18.12.0, 19.0.0 - [Clustered Data Ontap](https://www.precursorintelligence.com/product/netapp/clustered_data_ontap) by [Netapp](https://www.precursorintelligence.com/vendors/netapp) (Application): version not specified ## How do I fix CVE-2022-3602? 1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list. 2. **Apply the vendor’s fix.** Install the update named in the vendor’s advisory. We’ve put the advisory first in the list. 3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in. 4. **Keep an eye on it.** Track the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood. ### References - [openssl.org](https://www.openssl.org/news/secadv/20221101.txt) (Vendor advisory) - [packetstormsecurity.com](http://packetstormsecurity.com/files/169687/OpenSSL-Security-Advisory-20221101.html) (Third-party advisory, Vulnerability database) - [openwall.com](http://www.openwall.com/lists/oss-security/2022/11/01/15) (Mailing list, Third-party advisory) - [openwall.com](http://www.openwall.com/lists/oss-security/2022/11/01/16) (Mailing list, Third-party advisory) - [openwall.com](http://www.openwall.com/lists/oss-security/2022/11/01/17) (Mailing list, Third-party advisory) - [openwall.com](http://www.openwall.com/lists/oss-security/2022/11/01/18) (Mailing list, Third-party advisory) - [openwall.com](http://www.openwall.com/lists/oss-security/2022/11/01/19) (Mailing list, Third-party advisory) - [openwall.com](http://www.openwall.com/lists/oss-security/2022/11/01/20) (Mailing list, Third-party advisory) - [openwall.com](http://www.openwall.com/lists/oss-security/2022/11/01/21) (Mailing list, Third-party advisory) - [openwall.com](http://www.openwall.com/lists/oss-security/2022/11/01/24) (Mailing list, Third-party advisory) - [openwall.com](http://www.openwall.com/lists/oss-security/2022/11/02/1) (Mailing list, Third-party advisory) - [openwall.com](http://www.openwall.com/lists/oss-security/2022/11/02/10) (Mailing list, Third-party advisory) - [openwall.com](http://www.openwall.com/lists/oss-security/2022/11/02/11) (Mailing list, Third-party advisory) - [openwall.com](http://www.openwall.com/lists/oss-security/2022/11/02/12) (Mailing list, Third-party advisory) - [openwall.com](http://www.openwall.com/lists/oss-security/2022/11/02/13) (Mailing list, Third-party advisory) - [openwall.com](http://www.openwall.com/lists/oss-security/2022/11/02/14) (Mailing list, Third-party advisory) - [openwall.com](http://www.openwall.com/lists/oss-security/2022/11/02/15) (Mailing list, Third-party advisory) - [openwall.com](http://www.openwall.com/lists/oss-security/2022/11/02/2) (Mailing list, Third-party advisory) - [openwall.com](http://www.openwall.com/lists/oss-security/2022/11/02/3) (Mailing list, Third-party advisory) - [openwall.com](http://www.openwall.com/lists/oss-security/2022/11/02/5) (Mailing list, Third-party advisory) - [openwall.com](http://www.openwall.com/lists/oss-security/2022/11/02/6) (Mailing list, Third-party advisory) - [openwall.com](http://www.openwall.com/lists/oss-security/2022/11/02/7) (Mailing list, Third-party advisory) - [openwall.com](http://www.openwall.com/lists/oss-security/2022/11/02/9) (Mailing list, Third-party advisory) - [openwall.com](http://www.openwall.com/lists/oss-security/2022/11/03/1) (Mailing list, Third-party advisory) - [openwall.com](http://www.openwall.com/lists/oss-security/2022/11/03/10) (Mailing list, Third-party advisory) - [openwall.com](http://www.openwall.com/lists/oss-security/2022/11/03/11) (Mailing list, Third-party advisory) - [openwall.com](http://www.openwall.com/lists/oss-security/2022/11/03/2) (Mailing list, Third-party advisory) - [openwall.com](http://www.openwall.com/lists/oss-security/2022/11/03/3) (Mailing list, Third-party advisory) - [openwall.com](http://www.openwall.com/lists/oss-security/2022/11/03/5) (Mailing list, Third-party advisory) - [openwall.com](http://www.openwall.com/lists/oss-security/2022/11/03/6) (Mailing list, Third-party advisory) - [openwall.com](http://www.openwall.com/lists/oss-security/2022/11/03/7) (Mailing list, Third-party advisory) - [openwall.com](http://www.openwall.com/lists/oss-security/2022/11/03/9) (Mailing list, Third-party advisory) - [git.openssl.org](https://git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=fe3b639dc19b325846f4f6801f2f4604f56e3de3) (Broken link, Third-party advisory) - [lists.fedoraproject.org](https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/63YRPWPUSX3MBHNPIEJZDKQT6YA7UF6S/) (Mailing list, Third-party advisory) - [lists.fedoraproject.org](https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/DWP23EZYOBDJQP7HP4YU7W2ABU2YDITS/) (Mailing list, Third-party advisory) - [psirt.global.sonicwall.com](https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2022-0023) (Third-party advisory) - [security.gentoo.org](https://security.gentoo.org/glsa/202211-01) (Issue tracking, Third-party advisory) - [security.netapp.com](https://security.netapp.com/advisory/ntap-20221102-0001/) (Third-party advisory) - [tools.cisco.com](https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-openssl-W9sdCc2a) (Third-party advisory) - [kb.cert.org](https://www.kb.cert.org/vuls/id/794340) (Third-party advisory, Government resource) ## Questions ### What is CVE-2022-3602? CVE-2022-3602 is a high-severity flaw in OpenSSL, published on 1 November 2022. It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can take it offline. ### How serious is CVE-2022-3602? It scores 7.5 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2022-3602 is 75 out of 100, which is High. Its action is "Patch now". Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month. ### Is CVE-2022-3602 being exploited? It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 91%. That can change at any time, which is why we keep watching. ### Which versions does CVE-2022-3602 affect? For OpenSSL: 3.0.0 to before 3.0.7. The record lists 4 products in all, each with its versions, under "Who is affected" on this page. ### How do I fix CVE-2022-3602? Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet. ## Does CVE-2022-3602 affect you? Precursor Intelligence keeps checking for you: - **Tell us what you run.** Pick your software from a list, or let us work it out from your website. - **We match it to every flaw.** Over 400,000 published flaws, checked against your list. - **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it. - **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools. Start free (no card, nothing to install): https://www.precursorintelligence.com/register Book a demo: https://www.precursorintelligence.com/contact