dbcve.org
Wildfly ElytronApplication · Redhat

CVE-2020-10714

HIGH · 7.5 CVSS v3.1 Published 2020-09-23
Fix available
A fix is available. Upgrade to 1.11.3 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

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 Elytron version 1.11.3.Final and before. When using WildFly Elytron FORM authentication with a session ID in the URL, an attacker could perform a session fixation attack. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.

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

This is a session fixation vulnerability in WildFly Elytron's FORM authentication mechanism. When session IDs are transmitted via URL parameters rather than secure cookies, an attacker can pre-establish a session ID and trick a user into authenticating, then hijack the now-validated session.

MitigationDisable URL-based session tracking in WildFly Elytron configuration and use cookie-only session management. Upgrade to WildFly Elytron 1.11.4.Final or later which addresses this session fixation issue.

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.11.3
Codeready StudioApplication
Affected:= 12.0
Descision ManagerApplication
Affected:= 7.0
Jboss FuseApplication
Affected:= 7.0.0
Process AutomationApplication
Affected:= 7.0
Oncommand InsightApplication
Affected:all versions

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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 WildFly Elytron version
    Locate the eltron JAR file or check the MANIFEST.MF within the wildfly-elytron JAR in the application's lib or modules directory. Alternatively, check the build manifest or dependency list for the wildfly-elytron artifact version.
    Affected if The installed version is WildFly Elytron version 1.11.3 or earlier (any version before 1.11.4.Final).
  2. Confirm FORM authentication is enabled
    Review the web.xml descriptor (or the equivalent Elytron configuration file such as the application-security-domain mapping or http-authentication-factory configuration) and look for FORM-based authentication configuration in the <login-config> section.
    Affected if The application uses <auth-method>FORM</auth-method> in the web.xml or equivalent Elytron configuration.
  3. Check session tracking configuration
    Inspect the WildFly Elytron configuration (typically in standalone.xml or standalone-full.xml under the <subsystem xmlns="urn:wildfly:elytron:..."/> section) for the http-listener settings. Look for the <session-cookie> configuration or any <tracking-mode> setting that specifies URL parameter usage.
    Affected if Session tracking is configured to pass session IDs via URL parameters (for example, if URL-ENCODED session tracking is enabled rather than COOKIE-only).
  4. Identify affected Red Hat product versions
    If using Red Hat Codeready Studio 12.0, Decision Manager 7.0, JBoss Fuse 7.0.0, or Process Automation 7.0, check the embedded WildFly or JBoss EAP version included with these products by examining the product's about or version information.
    Affected if The product bundles WildFly Elytron version 1.11.3 or earlier.

You are affected if your environment uses WildFly Elytron (or a Red Hat product that bundles it) version 1.11.3 or earlier AND uses FORM authentication with URL-based session tracking enabled.

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.11.3 or later
Fixed in 1.11.3
Interim mitigation

Disable URL-based session tracking in WildFly Elytron configuration and use cookie-only session management. Upgrade to WildFly Elytron 1.11.4.Final or later which addresses this session fixation issue.

Fix this in Wildfly Elytron Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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