It 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.
The product does not implement or incorrectly implements one or more security-relevant checks as specified by the design of a standardized algorithm, protocol, or technique.
Link | Tags |
---|---|
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-3894 | issue tracking vendor advisory |
https://access.redhat.com/errata/RHSA-2019:1107 | third party advisory vendor advisory |
https://access.redhat.com/errata/RHSA-2019:1108 | third party advisory vendor advisory |
https://access.redhat.com/errata/RHSA-2019:1106 | third party advisory vendor advisory |
https://access.redhat.com/errata/RHSA-2019:1140 | third party advisory vendor advisory |
https://security.netapp.com/advisory/ntap-20190517-0004/ | third party advisory |