# CVE-2023-1108: Undertow: infinite loop in sslconduit during close > An attacker can cause a denial of service in Undertow by triggering an infinite loop during SSL connection closure. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 14 Sep 2023 - **Updated:** 2 Aug 2024 - **Also known as:** DEBIAN-CVE-2023-1108, GHSA-m4mm-pg93-fv78, OESA-2023-1202, RHSA-2023:1185, UBUNTU-CVE-2023-1108 ## What is CVE-2023-1108? CVE-2023-1108 is a high-severity denial of service vulnerability in Netapp Oncommand Workflow Automation, published on 14 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description A flaw was found in undertow. This issue makes achieving a denial of service possible due to an unexpected handshake status updated in SslConduit, where the loop never terminates. Weakness: CWE-835 (Loop with Unreachable Exit Condition) ## Which versions are affected by CVE-2023-1108? 4 open source packages ship an affected version, including io.undertow:undertow-core. It affects 16 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `io.undertow:undertow-core` | Maven | All versions | 2.2.24.Final | | `io.undertow:undertow-core` | Maven | All versions | 2.2.24.Final | | `io.undertow:undertow-core` | Maven | From 2.3.0 | 2.3.5.Final | | `io.undertow:undertow-core` | Maven | From 2.3.0 | 2.3.5.Final | | `eap7-undertow` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:2.2.22-1.SP3_redhat_00002.1.el7eap | | `eap7-wildfly` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:7.4.9-6.GA_redhat_00004.1.el7eap | | `eap7-wildfly-java-jdk11` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:7.4.9-6.GA_redhat_00004.1.el7eap | | `eap7-wildfly-java-jdk8` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:7.4.9-6.GA_redhat_00004.1.el7eap | | `eap7-wildfly-javadocs` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:7.4.9-6.GA_redhat_00004.1.el7eap | | `eap7-wildfly-modules` | Red Hat:jboss_enterprise_application_platform:7.4::el7 | All versions | 0:7.4.9-6.GA_redhat_00004.1.el7eap | | `eap7-undertow` | Red Hat:jboss_enterprise_application_platform:7.4::el8 | All versions | 0:2.2.22-1.SP3_redhat_00002.1.el8eap | | `eap7-wildfly` | Red Hat:jboss_enterprise_application_platform:7.4::el8 | All versions | 0:7.4.9-6.GA_redhat_00004.1.el8eap | | `eap7-wildfly-javadocs` | Red Hat:jboss_enterprise_application_platform:7.4::el8 | All versions | 0:7.4.9-6.GA_redhat_00004.1.el8eap | | `eap7-wildfly-modules` | Red Hat:jboss_enterprise_application_platform:7.4::el8 | All versions | 0:7.4.9-6.GA_redhat_00004.1.el8eap | | `eap7-undertow` | Red Hat:jboss_enterprise_application_platform:7.4::el9 | All versions | 0:2.2.22-1.SP3_redhat_00002.1.el9eap | | `eap7-wildfly` | Red Hat:jboss_enterprise_application_platform:7.4::el9 | All versions | 0:7.4.9-6.GA_redhat_00004.1.el9eap | | `eap7-wildfly-javadocs` | Red Hat:jboss_enterprise_application_platform:7.4::el9 | All versions | 0:7.4.9-6.GA_redhat_00004.1.el9eap | | `eap7-wildfly-modules` | Red Hat:jboss_enterprise_application_platform:7.4::el9 | All versions | 0:7.4.9-6.GA_redhat_00004.1.el9eap | Products: Netapp Oncommand Workflow Automation, Redhat Build of Quarkus, Redhat Decision Manager, Redhat Fuse, Redhat Integration Camel K, Redhat Integration Service Registry, Redhat Jboss Enterprise Application Platform, Redhat Jboss Enterprise Application Platform Expansion Pack, Redhat Openshift Application Runtimes, Redhat Openshift Container Platform, Redhat Openshift Container Platform for Linuxone, Redhat Openshift Container Platform for Power, Redhat Openstack Platform, Redhat Process Automation, Redhat Single Sign-On, Redhat Undertow. ## How do I fix CVE-2023-1108? Upgrade io.undertow:undertow-core to a fixed version for your release line: 2.2.24.Final or 2.3.5.Final. ## Is CVE-2023-1108 being exploited? There is no known exploitation of CVE-2023-1108 in the wild and no public exploit code. ## Other vulnerabilities in Netapp Oncommand Workflow Automation - [CVE-2015-3292](https://insights.sbomify.com/CVE-2015-3292/): Code injection in n/a (critical 10.0) - [CVE-2016-1894](https://insights.sbomify.com/CVE-2016-1894/): Auth bypass in n/a (high 8.1) - [CVE-2019-5503](https://insights.sbomify.com/CVE-2019-5503/): Information disclosure in OnCommand Workflow Automation (medium 5.3) - [CVE-2024-21144](https://insights.sbomify.com/CVE-2024-21144/): Denial of service in Java SE JDK and JRE (low 3.7) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-1108 and fix it if it is affected. What it is: CVE-2023-1108 is a high-severity denial of service vulnerability in Netapp Oncommand Workflow Automation, published on 14 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2023-1108 in the wild and no public exploit code. Affected packages and fixed versions: - io.undertow:undertow-core (Maven): affected all versions; fixed in 2.2.24.Final - io.undertow:undertow-core (Maven): affected all versions; fixed in 2.2.24.Final - io.undertow:undertow-core (Maven): affected from 2.3.0; fixed in 2.3.5.Final - io.undertow:undertow-core (Maven): affected from 2.3.0; fixed in 2.3.5.Final Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2023-1108/ (Markdown: https://insights.sbomify.com/CVE-2023-1108/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-1108 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-1108 - OSV: https://osv.dev/vulnerability/CVE-2023-1108 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-1108/ Summaries are generated and may contain mistakes; the official description above is the record.