jdonextgen
commented
1 year ago We've upgraded OpenSSL to version 3.1.3 in the Mirth Connect Eclipse Temurin Docker images to address vulnerabilities that exist in OpenSSL 3.0.2.
Closed tbobrykozaki closed 1 year ago
jdonextgen
commented
1 year ago We've upgraded OpenSSL to version 3.1.3 in the Mirth Connect Eclipse Temurin Docker images to address vulnerabilities that exist in OpenSSL 3.0.2.
Scan Performed by Tenable.IO
Deployed in AWS GovCloud Base OS RHEL 8.8
Mirth 4.4.0 docker deployment output from docker exec -it ... /bin/bash -> openssl version OpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022)
Container locations found at /var/lib/docker/overlay2/2c8b674dbcaeba17980b1e73ffbca5b22ddff4bbb2ec5a99d2eb39065e8fd5a5/diff/usr/bin/openssl /var/lib/docker/overlay2/bd5700efed7d6206a58c205213a9d5205ac42759343c8a0f0975fba197057f85/merged/usr/bin/openssl /var/lib/docker/overlay2/3f7d8dcc7c2f2c95be10b79b32cef72d6524b5a263a2e74b02d11363e5be755f/diff/usr/bin/openssl /var/lib/docker/overlay2/56a86609a5c358b00335308a359f1488f072a6334a2581efff2500ec3ef757ee/diff/usr/bin/openssl /var/lib/docker/overlay2/c4e78ad6d7d8cc176098872c6bacea5353bf9de0df17865d3b09ba7b439931c2/merged/usr/bin/openssl
The version of OpenSSL installed on the remote host is prior to 3.0.7. It is, therefore, affected by multiple vulnerabilities as referenced in the 3.0.7 advisory.
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. (CVE-2022-3786)
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. (CVE-2022-3602)
Risk Information RISK FACTOR High CVSS BASE SCORE 7.8 CVSS TEMPORAL SCORE 5.8 CVSS VECTOR AV:N/AC:L/Au:N/C:N/I:N/A:C CVSS TEMPORAL VECTOR E:U/RL:OF/RC:C CVSS3 BASE SCORE 7.5 CVSS3 TEMPORAL SCORE 6.5 CVSS3 VECTOR AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H CVSS3 TEMPORAL VECTOR E:U/RL:O/RC:C IVAM SEVERITY I Vulnerability Information VULN PUBLISHED 10/31/2022 at 5:00 PM EXPLOITABILITY PATCH PUBLISHED 10/31/2022 at 5:00 PM CPE cpe:/a:openssl:openssl Reference Information CVE CVE-2022-3786, CVE-2022-3602 IAVA 2022-A-0452-S