CVE-2022-3602 (an email address 4-byte buffer overflow) and CVE-2022-3786 (and email address variable length buffer overflow) are the case numbers affecting OpenSSL version 3.0.0 and later and were fixed in OpenSSL 3.0.7.
CVE-2022-3602 is an arbitrary 4-byte stack buffer overflow that could trigger crashes or lead to remote code execution (RCE). CVE-2022-3786 can end up leveraged by threat actors from malicious email addresses to trigger a denial of service via a buffer overflow.
This issues does not impact releases prior to 3.0 because the bugs were introduced as part of punycode decoding functionality (currently only used for processing email address name constraints in X.509 certificates). This code was first introduced in OpenSSL 3.0.0. OpenSSL 1.0.2, 1.1.1 and other earlier versions are not affected.
“After the preannouncement and rampant nail biting, the release from OpenSSL today revealed a couple of high severity flaws that are not easy to exploit and only affect a small subset of OpenSSL implementations,” said Claire Tills, senior research engineer at Tenable. “CVE-2022-3786 and CVE-2022-3602 are buffer overflow vulnerabilities in OpenSSL versions 3.0.0 through 3.0.6. The most likely outcome of successful exploitation is denial of service, but remote code execution is possible if stack overflow protections aren’t in place. Both vulnerabilities have to be triggered after certificate chain signature verification, meaning an attacker would likely need to get their malicious certificate signed.
“Vendors have all sorts of rationales for the way they handle vulnerability disclosures, in this case, OpenSSL pre-announcing the vulnerability before it had completed its investigation meant that it had to adjust its description of the vulnerabilities and those responding to this situation may have unnecessarily burnt out resources. That being said, this is an opportunity for organizations to evaluate their response processes and understand what can be improved. How difficult was it for them to determine which version of OpenSSL they had deployed, or whether any software on which they rely was vulnerable? Were their communication channels mature enough to get correct information to the people who needed it as soon as it was available?” Tills said.
“Patching this new OpenSSL vulnerability is just the start, as it demonstrates how machine identities can be broken, allowing threat actors to masquerade as trusted services,” said Kevin Bocek, vice president of security strategy and threat intelligence at Venafi. “Whether we’re running in the cloud in Azure, using Kubernetes in Amazon AWS, or using Apache in your datacenter, the entire digital business requires safe authentication of machine identities. The vulnerabilities in OpenSSL show the impact of poor machine identity management – specifically authenticating machine identities – opening the door to attackers.
“The current lack of visibility of complex cloud environments leaves businesses dangerously open to attack. Cloud is an untapped war front for threat actors, and I suspect we’ll see a lot more attacks on cloud native environments over the next few months. There’s a knowledge gap on both the threat actor and security sides, so we’re yet to truly understand the security implications, the attacks we might face, and vulnerabilities we may uncover. As we develop a deeper understanding of these complex environments, we’ll see a lot more critical vulnerabilities and high-impact attacks unearthed.
“Now that the seriousness of this vulnerability has been disclosed, it is likely that threat actors are already looking to take advantage of it. To protect themselves, organizations must prioritize patching, and fast,” Bocek said.

