AmqApplication · Redhat
CVE-2020-14297
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 discovered in Wildfly's EJB Client as shipped with Red Hat JBoss EAP 7, where some specific EJB transaction objects may get accumulated over the time and can cause services to slow down and eventaully unavailable. An attacker can take advantage and cause denial of service attack and make services unavailable.
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 in Wildfly's EJB Client (JBoss EAP 7) causes EJB transaction objects to accumulate over time without proper cleanup, progressively degrading service performance until complete unavailability occurs.
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
AmqApplication
= 2.0
Jboss Ejb ClientApplication
>= 1.0.0, < 4.0.34
Jboss Enterprise Application Platform Continuous DeliveryApplication
all versions
Jboss FuseApplication
= 6.0.0
Openshift Application RuntimesApplication
all versions
Single Sign OnApplication
= 7.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 JBoss EJB Client library in useSearch for jboss-ejb-client JAR files or dependencies in your application deployment (check lib/ or WEB-INF/lib directories, or Maven/Gradle dependency listings)Affected if The jboss-ejb-client library is present in the deployment
-
Check jboss-ejb-client versionExamine the JAR file manifest or dependency manager output for the exact version number of jboss-ejb-clientAffected if Version is found to be >= 1.0.0 and < 4.0.34
-
Verify EJB client usageConfirm the application makes use of EJB remote calls or EJB invocation mechanisms (look for javax.ejb.* imports, EJB annotations, or jboss-ejb-client context lookups in application code)Affected if EJB client functionality is actively used by the application
-
Monitor for transaction object accumulationUse JVM memory profiling tools (like VisualVM, JConsole, or heap dumps) to observe if EJB transaction-related objects (TransactionEntity, EJBTransaction) are growing in memory over time under loadAffected if Memory usage continuously grows without garbage collection reclaiming EJB transaction objects
You are affected if jboss-ejb-client version 1.0.0 through 4.0.33 is in use and the application utilizes EJB client features, causing progressive memory accumulation of transaction objects.
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 data4.0.34
Apply the vendor-supplied patch or upgrade JBoss EAP to a version that addresses the EJB transaction object accumulation issue.
Fix this in Amq
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14297 — 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-14297 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