WildflyApplication · Redhat
CVE-2019-3894
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 · uneditedIt was discovered that the ElytronManagedThread in Wildfly's Elytron subsystem in versions from 11 to 16 stores a SecurityIdentity to run the thread as. These threads do not necessarily terminate if the keep alive time has not expired. This could allow a shared thread to use the wrong security identity when executing.
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 confidenceThe ElytronManagedThread in WildFly Elytron versions 11-16 stores a SecurityIdentity for thread execution. When threads are reused via keep-alive without proper cleanup, a subsequent task on that shared thread may execute with the wrong security identity, potentially leading to privilege escalation or unauthorized access.
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
>= 11.0.0, <= 16.0.0
Jboss Enterprise Application PlatformApplication
= 7.0.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed WildFly or JBoss EAP versionRun 'grep -r "Red Hat" $JBOSS_HOME/" or check $JBOSS_HOME/bin/launch.sh for version strings. Also check $JBOSS_HOME/modules/org/jboss/as/server/main/module.xml for version metadata.Affected if The version is between 11.0.0 and 16.0.0 inclusive, or is exactly 7.0.0 for JBoss EAP
-
Verify the Elytron subsystem is present and enabledCheck for the presence of the Elytron subsystem configuration in the standalone.xml or domain.xml configuration file. Look for <subsystem xmlns="urn:wildfly:elytron:*" ...> within the configuration.Affected if The Elytron security subsystem is configured and active in the server configuration
-
Confirm thread pool keep-alive configuration is in useReview the server configuration (standalone.xml) for thread pool definitions. Look for <thread-pool> elements with keep-alive-time settings, or check the Elytron thread-factory configuration. The vulnerability triggers when threads are reused via keep-alive without cleanup.Affected if A thread pool with keep-alive settings is configured and threads are being reused
-
Check for custom SecurityIdentity thread executionReview application code or custom security configurations that may use ElytronManagedThread for executing tasks with specific security identities. Check for usages of SecurityIdentity.runAs() or similar Elytron identity execution methods.Affected if The server executes tasks using Elytron's SecurityIdentity with thread reuse enabled
A user is affected if they run WildFly versions 11.0.0 through 16.0.0 or JBoss EAP 7.0.0, have the Elytron subsystem enabled, and use thread pools with keep-alive that may reuse threads across different security contexts.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade WildFly to version 17 or later where this issue is fixed, or apply the vendor-provided patch if available for supported versions.
Fix this in Wildfly
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3894 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-3894 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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