dbcve.org
AmqApplication · Redhat

CVE-2020-14307

MEDIUM · 6.5 CVSS v3.1 Published 2020-07-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 vulnerability was found in Wildfly's Enterprise Java Beans (EJB) versions shipped with Red Hat JBoss EAP 7, where SessionOpenInvocations are never removed from the remote InvocationTracker after a response is received in the EJB Client, as well as the server. This flaw allows an attacker to craft a denial of service attack to make the service 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 confidence

A memory leak vulnerability exists in Wildfly's EJB implementation where SessionOpenInvocations are never removed from the remote InvocationTracker after responses are received, both on the EJB client and server sides. This causes unbounded resource accumulation leading to denial of service when the service becomes unavailable due to resource exhaustion.

MitigationApply the vendor patch or upgrade JBoss EAP to a version that addresses this vulnerability. Consider implementing resource monitoring and cleanup as a compensating control until the patch can be applied.

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
Affected:= 2.0
Jboss Enterprise Application Platform Continuous DeliveryApplication
Affected:all versions
Jboss FuseApplication
Affected:= 6.0.0
Openshift Application RuntimesApplication
Affected:all versions
Single Sign OnApplication
Affected:= 7.0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Wildfly/JBoss installation
    Locate the JBoss or Wildfly installation directory and check the version banner or manifest files. For Red Hat products, check /opt/jboss-*/ or the installation path for version files.
    Affected if The installed product is Wildfly, JBoss EAP, or any Red Hat product listed in the affected versions (Amq 2.0, Jboss Fuse 6.0.0, Openshift Application Runtimes, Single Sign On 7.0).
  2. Verify EJB remoting is in use
    Inspect the application server configuration for EJB connector or remoting endpoints. Check standalone.xml or the equivalent configuration file for <remoting> connectors or EJB-related thread pool configurations.
    Affected if EJB remoting connectors are configured and actively used by deployed applications, as the vulnerability affects remote EJB invocation tracking.
  3. Confirm InvocationTracker involvement
    Review server logs and heap dumps for references to org.jboss.ejb.client.remoting.InvocationTracker or SessionOpenInvocations classes. Use jmap or jcmd to analyze heap composition for accumulation of invocation-related objects.
    Affected if The InvocationTracker class is present in the runtime and SessionOpenInvocations objects are observed accumulating in heap memory over time.
  4. Monitor memory growth pattern
    Take multiple heap dumps over a period of time under normal load. Compare heap sizes and look for continuous growth in EJB-related object allocations, specifically related to remote call tracking.
    Affected if Memory usage continuously grows without stabilization, with EJB invocation tracking objects comprising an increasing percentage of heap space.

You are affected if you run any of the listed Red Hat products with EJB remoting enabled and observe unbounded memory growth linked to SessionOpenInvocations in the InvocationTracker.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch or upgrade JBoss EAP to a version that addresses this vulnerability. Consider implementing resource monitoring and cleanup as a compensating control until the patch can be applied.

Fix this in Amq Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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