Jboss Enterprise Application PlatformApplication · Redhat
CVE-2020-14384
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 JBossWeb in versions before 7.5.31.Final-redhat-3. The fix for CVE-2020-13935 was incomplete in JBossWeb, leaving it vulnerable to a denial of service attack when sending multiple requests with invalid payload length in a WebSocket frame. The highest threat from this vulnerability is to system availability.
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 confidenceA denial of service vulnerability exists in JBossWeb versions before 7.5.31.Final-redhat-3. The fix for CVE-2020-13935 (HTTP/2 vulnerability) was incomplete in the WebSocket handling code, leaving the system vulnerable to DoS attacks when processing multiple requests with invalid payload length in WebSocket frames.
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
Jboss Enterprise Application PlatformApplication
= 6.0.0
JbosswebApplication
< 7.5.31.final-redhat-3CVSS 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 JBossWeb or JBoss EAP installationLook for JBoss installation directories such as $JBOSS_HOME or common paths like /opt/jboss, /usr/share/jboss, or check for process running jboss or jbosswebAffected if JBossWeb or JBoss Enterprise Application Platform is installed and running
-
Determine JBossWeb versionCheck for version file in the JBossWeb installation, commonly found in a version.txt or release notes, or look at the jar file manifest for jbossweb.jarAffected if The installed version is below 7.5.31.Final-redhat-3 (for JBossWeb) or if running JBoss EAP 6.0.0 specifically
-
Check if WebSocket support is enabledReview the JBossWeb or JBoss EAP configuration files (such as standalone.xml or web.xml) for WebSocket protocol configuration or the presence of websocket-enabled flagsAffected if WebSocket support is enabled in the configuration; the vulnerability only applies when WebSocket handling code is active
-
Verify application uses WebSocket endpointsInspect deployed web applications for WebSocket endpoint definitions in deployment descriptors or annotated classes (javax.websocket or jakarta.websocket endpoints)Affected if Any deployed application uses WebSocket endpoints, as the vulnerable code path is triggered during WebSocket frame processing
-
Confirm version is within affected rangeCompare the identified JBossWeb version against the affected range: any version less than 7.5.31.Final-redhat-3, or specifically JBoss EAP 6.0.0Affected if The installed version is JBossWeb < 7.5.31.Final-redhat-3 or JBoss EAP 6.0.0
A user is affected if they are running JBossWeb version below 7.5.31.Final-redhat-3 (or JBoss EAP 6.0.0) with WebSocket support enabled and applications using WebSocket endpoints.
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.
From vendor data7.5.31.final-redhat-3
Update JBossWeb to version 7.5.31.Final-redhat-3 or later, which contains the complete fix for the incomplete CVE-2020-13935 patch.
Fix this in Jboss Enterprise Application Platform
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing6.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 $3,552.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14384 — 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-2020-14384 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