dbcve.org
UndertowApplication · Redhat

CVE-2020-10719

MEDIUM · 6.5 CVSS v3.1 Published 2020-05-26
Fix available
A fix is available. Upgrade to 2.1.1 / 7.3.13 or later.
See remediation →
74/100
Remediation priority · Elevated
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 in versions before 2.1.1.Final, regarding the processing of invalid HTTP requests with large chunk sizes. This flaw allows an attacker to take advantage of HTTP request smuggling.

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

Undertow before 2.1.1.Final contains a flaw in processing invalid HTTP requests with large chunk sizes, allowing HTTP request smuggling attacks. This occurs when the server incorrectly handles malformed chunked transfer encoding, potentially enabling attackers to bypass security controls by smuggling malicious requests through reverse proxies.

MitigationUpgrade Undertow to version 2.1.1.Final or later to patch the vulnerability. Additionally, configure proper frontend/backend timeout settings and connection handling to mitigate potential request smuggling vectors.

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
UndertowApplication
Affected:< 2.1.1
FuseApplication
Affected:= 1.0
Jboss Enterprise Application PlatformApplication
Affected:all versions= 7.3= 7.4= 7.2
Openshift Application RuntimesApplication
Affected:all versions
Single Sign OnApplication
Affected:all versions
Active Iq Unified ManagerApplication
Affected:all versions
Oncommand InsightApplication
Affected:< 7.3.13
Oncommand Workflow AutomationApplication
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
Low
Integrity
Low
Availability
None

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

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
    Search for undertow-core JAR files in the application lib/deployment directories, or check Java classpath for io.undertow classes using: find . -name 'undertow-core*.jar' or grep -r 'io.undertow' --include='*.jar' in deployment artifacts
    Affected if Undertow JAR files are found in the deployment or application runtime
  2. Determine Undertow version
    Check the undertow-core JAR filename for version, or inspect META-INF/MANIFEST.MF inside the JAR for Implementation-Version, or grep for undertow.version in pom.xml build files
    Affected if Installed version is lower than 2.1.1.Final (e.g., 2.1.0.Final, 2.0.x, 1.x)
  3. Check if HTTP listeners accept chunked transfer encoding
    Review Undertow handler configuration files or Java code that sets up Undertow servers. Look for exchange of transfer-encoding: chunked in request handling paths. In JBoss/Wildfly, check standalone.xml for http-listener with 'decode-urls' and 'record-request-start-time' settings
    Affected if The Undertow server is configured to handle HTTP requests with chunked transfer encoding (default behavior)
  4. Identify if behind a reverse proxy
    Inspect deployment architecture documentation or network configuration for presence of mod_cluster, Apache httpd, Nginx, or other reverse proxies fronting Undertow
    Affected if A reverse proxy or load balancer sits in front of the Undertow server
  5. Audit proxy timeout and connection handling settings
    Review proxy configuration (e.g., httpd proxy timeout, mod_cluster settings, Nginx proxy_read_timeout) and Undertow connection settings. Check for mismatched timeout values between frontend and backend
    Affected if Proxy and Undertow have misaligned timeouts or connection reuse settings that could enable request smuggling

You are affected if Undertow version is below 2.1.1.Final AND the server processes HTTP requests using chunked transfer encoding, especially when deployed behind a reverse proxy with potentially mismatched connection handling.

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
Upgrade available Upgrade to 2.1.1 / 7.3.13 or later
Fixed in 2.1.17.3.13
Interim mitigation

Upgrade Undertow to version 2.1.1.Final or later to patch the vulnerability. Additionally, configure proper frontend/backend timeout settings and connection handling to mitigate potential request smuggling vectors.

Fix this in Undertow Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-10719 — 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-2020-10719 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