dbcve.org
Jboss FuseApplication · Redhat

CVE-2020-10718

HIGH · 7.5 CVSS v3.1 Published 2020-09-16
Fix available
A fix is available. Upgrade to 13.0.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 flaw was found in Wildfly before wildfly-embedded-13.0.0.Final, where the embedded managed process API has an exposed setting of the Thread Context Classloader (TCCL). This setting is exposed as a public method, which can bypass the security manager. The highest threat from this vulnerability is to confidentiality.

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 · moderate confidence

A vulnerability in WildFly's embedded managed process API exposes the Thread Context Classloader (TCCL) setting through a public method, allowing attackers to manipulate the TCCL and bypass the security manager. This can lead to unauthorized access to privileged operations and confidentiality breaches.

MitigationUpgrade to WildFly 13.0.0.Final or later to obtain the fixed version. If immediate upgrading is not feasible, implement additional access controls around the affected embedded managed process API to restrict TCCL manipulation.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 installation and version
    Locate the WildFly installation directory. Check for a 'wildfly-core-*.jar' or 'jboss-modules.jar' file, or inspect the 'modules/org/wildfly/core/main' directory for version markers. Run 'grep -r "13.0.0" <install_dir>' or check the server startup logs for the exact version string.
    Affected if The installed WildFly version is less than 13.0.0 (for example, 12.x, 11.x, 10.x)
  2. Identify JBoss Fuse installation and version
    Locate the JBoss Fuse installation. Check the 'jboss-fuse-*' directory name for the version or examine the 'system/org/jboss/fuse/fuse-main' directory for version metadata. Look for version files in the 'bin' or 'lib' directories.
    Affected if The installed JBoss Fuse version equals exactly 7.0.0
  3. Verify if the embedded managed process API is in use
    Search application code and configuration for usage of classes from 'org.wildfly.core.embedded' package, specifically 'ManagedProcess' or related embedded API classes. Check standalone.xml for embedded server configurations or custom startup scripts that instantiate embedded containers.
    Affected if Code or configuration references the WildFly embedded managed process API (package: org.wildfly.core.embedded)
  4. Check if security manager is enabled
    Examine the standalone.xml configuration file in the 'app/server/configuration' directory for '<security-manager>' elements. Also check for '-secmgr' startup argument in startup scripts or the JAVA_OPTS environment variable.
    Affected if A security manager is configured and the WildFly/JBoss Fuse version is vulnerable (less than 13.0.0)

You are affected if you run WildFly versions below 13.0.0 or JBoss Fuse 7.0.0, and your applications or configurations use the embedded managed process API while relying on a security manager for access control.

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 13.0.0 or later
Fixed in 13.0.0
Interim mitigation

Upgrade to WildFly 13.0.0.Final or later to obtain the fixed version. If immediate upgrading is not feasible, implement additional access controls around the affected embedded managed process API to restrict TCCL manipulation.

Fix this in Jboss Fuse Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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