dbcve.org
WildflyApplication · Redhat

CVE-2020-10740

HIGH · 7.5 CVSS v3.1 Published 2020-06-22
Fix available
A fix is available. Upgrade to 20.0.0 or later.
See remediation →
81/100
Remediation priority · High
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 in versions before 20.0.0.Final, where a remote deserialization attack is possible in the Enterprise Application Beans(EJB) due to lack of validation/filtering capabilities in wildfly.

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

Wildfly versions before 20.0.0.Final contain a remote deserialization vulnerability in the Enterprise Application Beans (EJB) subsystem. The application server lacks proper validation and filtering capabilities when deserializing objects in EJB invocations, allowing remote attackers to potentially execute arbitrary code by sending crafted serialized objects.

MitigationUpgrade Wildfly to version 20.0.0.Final or later which includes the necessary validation/filtering for EJB deserialization. If immediate upgrade is not feasible, restrict network access to the EJB endpoints and consider disabling EJB if not required.

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
WildflyApplication
Affected:< 20.0.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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/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 the installed Wildfly version
    Check the version file in the Wildfly installation directory, or run the version.sh script, or look at the output of the --version flag. Common locations include $WILDFLY_HOME/wildfly-version.txt or check the pom.xml if source is available.
    Affected if The installed version is any release before 20.0.0.Final (e.g., 19.x, 18.x, 17.x, etc.)
  2. Locate the EJB subsystem configuration
    Open the standalone.xml or domain.xml configuration file (typically in $WILDFLY_HOME/standalone/configuration/ or $WILDFLY_HOME/domain/configuration/) and search for the <subsystem> element with namespace related to ejb3.
    Affected if An ejb3 subsystem is defined and present in the configuration file, indicating EJB is enabled.
  3. Confirm EJB remote invocation is enabled
    In the standalone.xml, look for <remote> within the ejb3 subsystem configuration. Check for <channel> elements or <remoting> configurations that expose EJB over remoting protocols. Also verify if the remoting subsystem is bound to a network-accessible interface.
    Affected if The EJB subsystem contains remote client invocations configured (typically with remoting connectors) and the interface is bound to a non-localhost address.
  4. Identify exposed EJB ports
    Check the socket-binding-group in standalone.xml for remoting or http-rmi ports (commonly port 8080 for HTTP or 4447 for remoting). Verify which network interfaces these bindings use.
    Affected if EJB-related ports (4447, 8080, 8181, or custom remoting ports) are bound to 0.0.0.0 or a routable IP address rather than localhost only.

The environment is affected if Wildfly version is before 20.0.0.Final AND the EJB3 subsystem with remote invocation capabilities is configured and network-accessible.

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
Upgrade available Upgrade to 20.0.0 or later
Fixed in 20.0.0
Interim mitigation

Upgrade Wildfly to version 20.0.0.Final or later which includes the necessary validation/filtering for EJB deserialization. If immediate upgrade is not feasible, restrict network access to the EJB endpoints and consider disabling EJB if not required.

Fix this in Wildfly Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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 locally
dbcve dependency scanner

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