Jboss RemotingApplication · Redhat
CVE-2019-19343
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 when using Remoting as shipped in Red Hat Jboss EAP before version 7.2.4. A memory leak in HttpOpenListener due to holding remote connections indefinitely may lead to denial of service. Versions before undertow 2.0.25.SP1 and jboss-remoting 5.0.14.SP1 are believed to be vulnerable.
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 memory leak exists in Undertow's HttpOpenListener when using JBoss Remoting. The listener holds remote connections indefinitely without proper cleanup, causing memory to accumulate over time until the application becomes unresponsive due to exhaustion.
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 RemotingApplication
< 5.0.14= 5.0.14
Jboss Enterprise Application PlatformApplication
< 7.2.4
UndertowApplication
< 2.0.25= 2.0.25
Active Iq Unified ManagerApplication
all 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 Undertow versionCheck the undertow-core JAR file version in your deployment (typically in WEB-INF/lib or the classpath), or query the server for its Undertow component version via management console or pom.xml dependenciesAffected if Undertow version is lower than 2.0.25 or equals 2.0.25 (versions 2.0.25.SP1 and later are not affected)
-
Identify JBoss Remoting versionCheck the jboss-remoting JAR file version in your deployment or classpath, typically named jboss-remoting-*.jarAffected if JBoss Remoting version is lower than 5.0.14 or equals 5.0.14 (versions 5.0.14.SP1 and later are not affected)
-
Identify JBoss Enterprise Application Platform versionCheck the JBoss EAP version via the server startup logs, management console, or ps aux | grep jboss outputAffected if JBoss EAP version is lower than 7.2.4 (version 7.2.4 and later are not affected)
-
Confirm JBoss Remoting is in useInspect your application configuration for JBoss Remoting dependencies or RemotingConnector usage in standalone.xml or jboss-deployment-structure.xmlAffected if JBoss Remoting is actively loaded or configured in the server - the vulnerability only manifests when Undertow uses JBoss Remoting for remote connections
-
Check for NetApp Active IQ Unified ManagerDetermine if the environment includes NetApp Active IQ Unified Manager softwareAffected if NetApp Active IQ Unified Manager is present - all versions are affected
You are affected if you are running any affected version of Undertow (below 2.0.25), JBoss Remoting (below 5.0.14), or JBoss EAP (below 7.2.4) with JBoss Remoting enabled, or any version of NetApp Active IQ Unified Manager.
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 data2.0.255.0.147.2.4
Upgrade to Undertow 2.0.25.SP1 or later, JBoss Remoting 5.0.14.SP1 or later, or JBoss EAP 7.2.4 or later to resolve the connection cleanup issue.
Fix this in Jboss Remoting
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19343 — 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-2019-19343 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