THE THREAT
On November 1st, 2022, OpenSSL disclosed two high severity vulnerabilities impacting OpenSSL versions above 3.0.0 and below the patched version of 3.0.7, as well as applications with an affected OpenSSL library embedded. The notable vulnerability is tracked as CVE-2022-3602: a Buffer Overflow vulnerability. A threat actor may exploit CVE-2022-3602 to cause Denial-of-Service (DoS) or Remote Code Execution (RCE). In an attack scenario, this vulnerability is most likely to be exploited in email-based attacks, although remote attacks are possible in certain configurations. Currently, there is no indication of real-world attacks or publicly available Proof-of-Concept (PoC) exploit code.
All systems using vulnerable versions (3.0.0 -> 3.0.6) should apply the patch as soon as possible. Due to the scope of OpenSSL use, the vulnerability impacts many products and vendors will be required to release updates. The eSentire Threat Intelligence team assesses with medium confidence that threat actors will exploit this vulnerability in the future.
What we’re doing about it
- eSentire Managed Vulnerability Service (MVS) will add plugins for this vulnerability when they become available
- eSentire security teams are tracking this vulnerability for additional details and detection opportunities
What you should do about it
- Verify potentially impacted software using the following list, produced by NCSC https://github.com/NCSC-NL/OpenSSL-2022/blob/main/software/README.md
- After performing a business impact review, apply the relevant security patches from OpenSSL
- The command # OpenSSL version can be executed to determine your version number
- Apply vendor updates as they become available
Additional information
OpenSSL is a library used for cryptographic purposes, especially in network connections. For example, web servers often use OpenSSL to establish encrypted HTTPS connections. In addition, mail servers and VPN protocols such as OpenVPN also use OpenSSL to establish encrypted communication channels. The library can be found in many products, including network devices, embedded systems, and container images.
The pre-announcements of CVE-2022-3602 described this issue as CRITICAL. Further analysis has led this to be downgraded to HIGH as it cannot be exploited in most widely used architectures and platforms. Exploitation would require a vulnerable TLS client to connect to a malicious server. Further, the bugs were introduced as part of Punycode decoding functionality, which is currently only used for processing email address name constraints in X.509 certificates. However, any OpenSSL 3.0 application that verifies X.509 certificates received from untrusted sources, should be considered vulnerable. This includes TLS clients and TLS servers configured to use TLS client authentication.
Docker has stated publicly that approximately 1000 images are impacted and will be mitigated shortly – please follow Docker guidance here.
The second vulnerability addressed by OpenSSL on November 1st, 2022, is CVE-2022-3786. This is a buffer overflow vulnerability that may result in Denial-of-Service. OpenSSL 3.0.7 addresses both CVE-2022-3786 and CVE-2022-3602.
Known Impacted Products: (Note: This list is not exhaustive)
- OpenMandriva Cooker
- Fedora 36, Fedora Rawhide
- Kali 2022.3
- Mageia Cauldron
- OpenMandriva 4.3
- Linux Mint 21 Vanessa
- Ubuntu 22.04
- Rocky Linux release 9.0 (Blue Onyx)
- CentOS Stream 9
- Redhat ES 9
- AlmaLinux OS Foundation 9
- Alpine Linux 3.0.5
- Amazon Linux 3.0.5-1
- Dockerhub 3.0.3
- Intel System Usage Report 3.0.2
- Offensive Security 3.0.5
- VMware 3.0.0
NCSC is maintaining a list of impacted and unaffected software. The page continues to be updated at the time of writing.
References:
[1] https://www.openssl.org/news/secadv/20221101.txt
[2] https://mta.openssl.org/pipermail/openssl-announce/2022-November/000241.html
[3] https://mta.openssl.org/pipermail/openssl-announce/2022-October/000238.html
[4] https://www.openssl.org/blog/blog/2022/11/01/email-address-overflows/
[5] https://github.com/NCSC-NL/OpenSSL-2022
[5] https://www.docker.com/blog/security-advisory-critical-openssl-vulnerability/
