OpenSSL Releases Patch for 2 New High
Vulnerabilities mentionedAll →
| CVE | Vulnerability | CVSS | EPSS | Flags | Affected | Exposure | Published |
|---|---|---|---|---|---|---|---|
| CVE-2014-0160 | Heartbleed: unauthenticated memory disclosure in OpenSSL TLS/DTLS heartbeat handling The flaw (CVE-2014-0160, widely known as 'Heartbleed') is an out-of-bounds read (CWE-125) in the TLS and DTLS implementations of OpenSSL, caused by improper handling of Heartbeat Extension packets. A remote, unauthenticated attacker triggers it by sending a crafted heartbeat request whose declared payload length exceeds the data actually sent, causing OpenSSL to copy up to roughly 64 KB of adjacent process memory into the response. The attacker gains chunks of process memory per request — potentially TLS private keys, session cookies, usernames and passwords — and can repeat the request to harvest more, typically without any trace in logs. Any server or client running a vulnerable OpenSSL release that enables TLS or DTLS heartbeats is affected, which at the time of disclosure included hundreds of thousands of internet-exposed HTTPS servers as well as appliances, load balancers, and bundled libraries. Exploitation is confirmed in the wild: the vulnerability is listed in CISA KEV (added 2022-05-04, required action: apply updates per vendor instructions) and EPSS assigns it the maximum 100% probability of exploitation within 30 days. Do: Apply OpenSSL updates per your OS or vendor's instructions — the upstream fix at the time of the 2014 disclosure was OpenSSL 1.0.1g, with most distributions shipping backported patches — and restart or rebuild every service linked against OpenSSL, including bundled copies in load balancers, appliances, and VPN or management interfaces. Because leaked memory can include TLS private keys, treat keys and certificates on affected endpoints as compromised: rotate keys, reissue and revoke certificates, and invalidate session cookies and credentials that may have leaked. Confirm the heartbeat fix is present on all TLS/DTLS endpoints to satisfy the CISA KEV required action. | — | 100% | KEV |
| mass≈500,000+ internet-exposed HTTPS servers at the time of disclosure, plus vastly larger embedded/library deployments | |
| CVE-2016-6309 | statem/statem.c in OpenSSL 1.1.0a does not consider memory-block movement after a realloc call, which allows remote attackers to cause a denial of service (use- statem/statem.c in OpenSSL 1.1.0a does not consider memory-block movement after a realloc call, which allows remote attackers to cause a denial of service (use-after-free) or possibly execute arbitrary code via a crafted TLS session. NVD description · AI analysis pending | 9.8 | 70% |
| — | ||
| CVE-2022-3786 +1 in the same advisory: …3602 | A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. 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 a malicious certificate or for an application to continue certificate verification despite failure to construct a path to a trusted issuer. An attacker can craft a malicious email address in a certificate to overflow an arbitrary number of bytes containing the `.' character (decimal 46) on the stack. This buffer overflow could result in a crash (causing a denial of service). 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. NVD description · AI analysis pending | 7.5 | 92% |
| — |
Full article827 words · extracted from thehackernews.com · click to collapse
The OpenSSL project has rolled out fixes to contain two high-severity flaws in its widely used cryptography library that could result in a denial-of-service (DoS) and remote code execution.
The issues, tracked as CVE-2022-3602 and CVE-2022-3786, have been described as buffer overrun vulnerabilities that can be triggered during X.509 certificate verification by supplying a specially-crafted email address.
"In a TLS client, this can be triggered by connecting to a malicious server," OpenSSL said in an advisory for CVE-2022-3786. "In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects."
OpenSSL is an open source implementation of the SSL and TLS protocols used for secure communication and is baked into several operating systems and a wide range of software.
Versions 3.0.0 through 3.0.6 of the library are affected by the new flaws, which has been remediated in version 3.0.7. It's worth noting that the commonly deployed OpenSSL 1.x versions are not vulnerable.
Per data shared by Censys, about 7,062 hosts are said to run a susceptible version of OpenSSL as of October 30, 2022, with a majority of those located in the U.S., Germany, Japan, China, Czechia, the U.K., France, Russia, Canada, and the Netherlands.
While CVE-2022-3602 was initially treated as a Critical vulnerability, its severity has since been downgraded to High, citing stack overflow protections in modern platforms. Security researchers Polar Bear and Viktor Dukhovni have been credited with reporting CVE-2022-3602 and CVE-2022-3786 on October 17 and 18, 2022.
The OpenSSL Project further noted the bugs were introduced in OpenSSL 3.0.0 as part of punycode decoding functionality that's currently used for processing email address name constraints in X.509 certificates.
Despite the change in severity, OpenSSL said it considers "these issues to be serious vulnerabilities and affected users are encouraged to upgrade as soon as possible."
Cybersecurity firm Rapid7 pointed out that "exploitability is significantly limited," as the flaws occur "after certificate 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."
"Specifically, implementations that are configured for mutual authentication, where both the client and the server are providing OpenSSL-provided certificates for authentication, should definitely be fast-tracking this update," Tod Beardsley, director of research at Rapid7, said.
Brian Fox, co-founder and CTO at software supply chain management firm Sonatype, reiterated the high level of difficulty required for weaponizing the flaws.
"The vulnerability requires a malformed certificate that is trusted or signed by a naming authority," Fox said. "That means that authorities should be able to quickly prevent certificates designed to target this vulnerability from being created, further limiting the scope."
Version 3.0, the current release of OpenSSL, is bundled with Linux operating system flavors such as CentOS, Fedora, Kali, Linux Mint, openSUSE Leap, and Ubuntu. Apple's macOS, on the other hand, uses LibreSSL. Container images built using affected versions of Linux are also impacted.
According to an advisory published by Docker, roughly 1,000 image repositories could be affected across various Docker Official Images and Docker Verified Publisher images.
"The new OpenSSL vulnerability does not affect the issuance or use of certificates," Tim Callan, chief compliance officer at Sectigo, said in a statement. "No organization needs to revoke or reissue certificates based on this vulnerability."
The last critical flaw addressed by OpenSSL was in September 2016, when it closed out CVE-2016-6309, a use-after-free bug that could result in a crash or execution of arbitrary code.
There are close to 240,000 publicly accessible servers worldwide running versions of OpenSSL that are still vulnerable to Heartbleed eight years after its initial discovery, Rezilion researchers Yotam Perkal and Ofri Ouzan said.
The OpenSSL software toolkit was most notably impacted by Heartbleed (CVE-2014-0160), a serious memory handling issue in the implementation of the TLS/DTLS heartbeat extension, enabling attackers to read portions of a target server's memory.
"A critical vulnerability in a software library like OpenSSL, which is so widely in use and so fundamental to the security of data on the internet, is one that no organization can afford to overlook," SentinelOne said.
That said, OpenSSL has warned that the vulnerability may be critical for systems that do not have adequate protections in place, theoretically leading to remote code execution on some architectures and platforms.
"The chance of this vulnerability getting exploited in the wild is low due to the sophistication of this security bug, and the fact that one of the conditions is a malicious certificate signed by a trusted CA," Bharat Jogi, director of vulnerability and threat research at Qualys, said.
"Seeing as most modern systems and platforms implement built-in protections to thwart these kinds of attacks and mitigate against these risks – specifically remote code execution – the level of severity was downgraded."
Found this article interesting? Follow us on Google News, Twitter and LinkedIn to read more exclusive content we post.
Text extracted automatically; images, tables and formatting may be missing. Original: https://thehackernews.com/2022/11/just-in-openssl-releases-patch-for-2.html