dbcve.org
Build Of QuarkusApplication · Redhat

CVE-2023-1108

HIGH · 7.5 CVSS v3.1 Published 2023-09-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A denial of service vulnerability exists in Undertow's SSL/TLS handshake handling (SslConduit). An unexpected handshake status update creates an infinite loop condition during the SSL handshake process, causing the affected thread to hang and making the service unavailable.

MitigationUpgrade Undertow to a patched version that addresses the handshake loop issue, or apply vendor-supplied security patches.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Build Of QuarkusApplication
Affected:all versions
Decision ManagerApplication
Affected:= 7.0
FuseApplication
Affected:= 1.0.0
Integration Camel KApplication
Affected:all versions
Integration Service RegistryApplication
Affected:all versions
Jboss Enterprise Application PlatformApplication
Affected:all versions= 7.4
Jboss Enterprise Application Platform Expansion PackApplication
Affected:all versions
Openshift Application RuntimesApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Undertow is in use
    Check application dependencies or server configuration for the undertow-core library. In Java applications, review the pom.xml, build.gradle, or runtime classpath for undertow-core. For Red Hat EAP, check the modules or libs directory for undertow jars.
    Affected if Undertow is present in the runtime environment
  2. Verify SSL/TLS is enabled on Undertow
    Inspect the Undertow server configuration for SSL/TLS listeners. Look for 'https', 'ssl', or 'tls' keywords in the server.xml, standalone.xml, or programmatic configuration. Check if an SSLContext is configured via SslConduit or UndertowBuilder.
    Affected if SSL/TLS is configured and the server accepts HTTPS connections on an Undertow-based service
  3. Confirm product and version against affected list
    Identify the specific Red Hat product in use (Quarkus, Decision Manager, Fuse, Camel K, Service Registry, JBoss EAP, or Openshift Application Runtimes) and determine its version. Compare against the affected versions: Quarkus all versions, Decision Manager 7.0, Fuse 1.0.0, Camel K all versions, Service Registry all versions, JBoss EAP all versions and 7.4, EAP Expansion Pack all versions, Openshift Application Runtimes all versions.
    Affected if The installed product matches any of the affected product/version combinations listed in the CVE

If Undertow is present, SSL/TLS is enabled, and the product version matches the affected list, the environment is vulnerable to the SSL handshake infinite loop causing denial of service.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Undertow to a patched version that addresses the handshake loop issue, or apply vendor-supplied security patches.

Fix this in Build Of Quarkus Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-1108 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-1108 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data