Build Of QuarkusApplication · Redhat
CVE-2022-1259
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 · uneditedA flaw was found in Undertow. A potential security issue in flow control handling by the browser over HTTP/2 may cause overhead or a denial of service in the server. This flaw exists because of an incomplete fix for CVE-2021-3629.
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 · moderate confidenceA flow control handling vulnerability in Undertow's HTTP/2 implementation allows browsers to cause overhead or denial of service. This is an incomplete fix for CVE-2021-3629, indicating the original patch did not fully address the HTTP/2 flow control issue.
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
all versions
Integration Camel KApplication
all versions
Jboss Enterprise Application PlatformApplication
= 7.0.0
Openshift Application RuntimesApplication
all versions
Single Sign OnApplication
= 7.0
UndertowApplication
<= 2.2.17= 2.2.18= 2.2.19
Active Iq Unified ManagerApplication
all versionsall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Undertow is in useCheck for undertow-core jar files in the application lib directory, or identify if the application runs on Red Hat JBoss EAP, Red Hat Quarkus, Red Hat Openshift Application Runtimes, or other Red Hat products that bundle Undertow. For NetApp products, check if the system runs Active IQ Unified Manager or Cloud Secure Agent.Affected if The application uses Undertow directly or through Red Hat JBoss EAP 7.0.0, Red Hat Quarkus (any version), Red Hat Camel K (any version), Red Hat Openshift Application Runtimes (any version), Red Hat Single Sign-On 7.0, or NetApp Active IQ Unified Manager or Cloud Secure Agent.
-
Determine Undertow versionIf using Undertow directly, check the version of undertow-core jar in the classpath or dependency management. If using Red Hat products, check the version of the Undertow component bundled with the product.Affected if Undertow version is 2.2.19, 2.2.18, or any version 2.2.17 or earlier.
-
Check if HTTP/2 is enabledInspect the application server or Undertow configuration for HTTP/2 protocol support. Look for 'h2' or 'HTTP/2' in connector or listener configurations, or check for the presence of the 'undertow-http2' module in the deployment.Affected if HTTP/2 protocol handling is enabled in the Undertow configuration.
-
Inspect HTTP/2 flow control configurationReview the Undertow server configuration for any non-default flow control settings related to HTTP/2 stream windows. Check for custom buffer pool or byte buffer allocator configurations that may affect HTTP/2 flow control handling.Affected if HTTP/2 is enabled and default flow control behavior is in use without additional restrictions on stream window sizes.
You are affected if your application uses Undertow with HTTP/2 enabled and the Undertow version is 2.2.19, 2.2.18, or any version 2.2.17 or earlier, or if you use any version of the listed Red Hat or NetApp products that bundle a vulnerable Undertow version.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedUpgrade Undertow to a version containing the complete fix for this vulnerability, or apply the corresponding patch that fully addresses the HTTP/2 flow control issue from CVE-2021-3629.
Undertow 2.2.20 or later (or corresponding patched version in Red Hat JBoss EAP 7.0+ or Red Hat Single Sign-On 7.0+)
- Identify the Undertow library version in use by examining project dependencies (Maven pom.xml, Gradle build.gradle, or container image SBOM)
- For Maven projects, locate undertow-core in pom.xml and note the current version
- For direct JAR usage, check the undertow-core JAR filename or examine META-INF/MANIFEST.MF inside the JAR
- Upgrade Undertow to version 2.2.20 or later by updating the dependency version in your build configuration
- Rebuild and redeploy the application, ensuring no transitive dependency conflicts arise
- Verify the upgrade by checking that the new Undertow version loads correctly at runtime
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Build Of Quarkus
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2022-1259 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-1259 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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