dbcve.org
Wildfly ElytronApplication · Redhat

CVE-2020-1748

HIGH · 7.5 CVSS v3.1 Published 2020-09-16
Fix available
A fix is available. Upgrade to 1.6.8.final-redhat-00001 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 all supported versions before wildfly-elytron-1.6.8.Final-redhat-00001, where the WildFlySecurityManager checks were bypassed when using custom security managers, resulting in an improper authorization. This flaw leads to information exposure by unauthenticated access to secure resources.

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

All supported versions of WildFly Elytron before 1.6.8.Final-redhat-00001 contain a flaw where WildFlySecurityManager authorization checks are bypassed when custom security managers are used. This improper authorization allows unauthenticated users to access otherwise secure resources, leading to information exposure.

MitigationUpgrade to wildfly-elytron-1.6.8.Final-redhat-00001 or later. If immediate upgrade is not possible, avoid deploying or using custom security managers in affected WildFly installations.

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
Wildfly ElytronApplication
Affected:< 1.6.8.final-redhat-00001
Decision ManagerApplication
Affected:= 7.0
Process AutomationApplication
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
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 Elytron version
    Locate the wildfly-elytron jar file or module in your installation (typically under $WILDFLY_HOME/modules/org/wildfly/security/elytron/main/) and check the version from the filename or manifest. Alternatively, check the release manifest file (META-INF/MANIFEST.MF) within the elytron module.
    Affected if The installed version is earlier than 1.6.8.final-redhat-00001 (for example 1.6.7.Final, 1.6.6.Final-redhat-00001, etc.)
  2. Determine if custom security managers are deployed
    Search your deployed applications and configuration for custom implementations of java.lang.SecurityManager or any subclasses that wrap or override the default WildFlySecurityManager. Check application codebases and EAR/WAR deployments for classes extending SecurityManager, Policy, or PermissionCollection.
    Affected if Custom security managers are deployed or configured in the Java runtime options (for example, -Djava.security.manager pointing to a custom class).
  3. Check Red Hat Decision Manager version
    If using Red Hat Decision Manager, check the installed version by inspecting the product manifest or version file (typically in /opt/rhdm-7.0/ or the installation directory). Query the product version via the management console or running 'rhdm-7.0-admin.sh --version' or equivalent.
    Affected if Version equals 7.0 and WildFly Elytron version is below 1.6.8.final-redhat-00001.
  4. Check Red Hat Process Automation version
    If using Red Hat Process Automation Manager, check the installed version by inspecting the product manifest or version file (typically in /opt/rhpam-7.0/ or the installation directory). Query the product version via the management console or running 'rhpam-7.0-admin.sh --version' or equivalent.
    Affected if Version equals 7.0 and WildFly Elytron version is below 1.6.8.final-redhat-00001.

You are affected if WildFly Elytron is installed at a version earlier than 1.6.8.final-redhat-00001 AND custom security managers are deployed or configured in the environment.

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 1.6.8.final-redhat-00001 or later
Fixed in 1.6.8.final-redhat-00001
Interim mitigation

Upgrade to wildfly-elytron-1.6.8.Final-redhat-00001 or later. If immediate upgrade is not possible, avoid deploying or using custom security managers in affected WildFly installations.

Fix this in Wildfly Elytron Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
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,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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