CVE-2019-3894 – wildfly: wrong SecurityIdentity for EE concurrency threads that are reused
https://notcve.org/view.php?id=CVE-2019-3894
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. Se descubrió que ElytronManagedThread del subsistemas Wildfly's Elytron en versiones desde 11 hasta la 16 almacena un SecurityIdentity para ejecutar el hilo. Estos hilos no necesariamente terminan si el tiempo de mantener activos no ha expirado. • https://access.redhat.com/errata/RHSA-2019:1106 https://access.redhat.com/errata/RHSA-2019:1107 https://access.redhat.com/errata/RHSA-2019:1108 https://access.redhat.com/errata/RHSA-2019:1140 https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-3894 https://security.netapp.com/advisory/ntap-20190517-0004 https://access.redhat.com/security/cve/CVE-2019-3894 https://bugzilla.redhat.com/show_bug.cgi?id=1682108 • CWE-358: Improperly Implemented Security Check for Standard •
CVE-2019-3805 – wildfly: Race condition on PID file allows for termination of arbitrary processes by local users
https://notcve.org/view.php?id=CVE-2019-3805
A flaw was discovered in wildfly versions up to 16.0.0.Final that would allow local users who are able to execute init.d script to terminate arbitrary processes on the system. An attacker could exploit this by modifying the PID file in /var/run/jboss-eap/ allowing the init.d script to terminate any process as root. Fue encontrado un fallo en las versiones de wildfly hasta la 16.0.0. Final que permitiría a los usuarios locales capaces de ejecutar el script init.d conllevar a procesos arbitrarios en el sistema. Un atacante podría explotar esto modificando el archivo PID en /var/run/jboss-eap/ permitiendo que el script init.d termine cualquier proceso como root. • https://access.redhat.com/errata/RHSA-2019:1106 https://access.redhat.com/errata/RHSA-2019:1107 https://access.redhat.com/errata/RHSA-2019:1108 https://access.redhat.com/errata/RHSA-2019:1140 https://access.redhat.com/errata/RHSA-2019:2413 https://access.redhat.com/errata/RHSA-2020:0727 https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-3805 https://security.netapp.com/advisory/ntap-20190517-0004 https://access.redhat.com/security/cve/CVE-2019-3805 https://bugzilla • CWE-269: Improper Privilege Management CWE-364: Signal Handler Race Condition •
CVE-2018-14627 – JBoss/WildFly: iiop does not honour strict transport confidentiality
https://notcve.org/view.php?id=CVE-2018-14627
The IIOP OpenJDK Subsystem in WildFly before version 14.0.0 does not honour configuration when SSL transport is required. Servers before this version that are configured with the following setting allow clients to create plaintext connections: <transport-config confidentiality="required" trust-in-target="supported"/> El subsistema IIOP OpenJDK en WildFly en versiones anteriores a la 14.0.0 no cumple con al configuración cuando se requiere transporte SSL. Los servidores con versiones anteriores a ésta que estén configurados con las siguientes opciones permiten que los clientes creen conexiones en texto plano: • https://access.redhat.com/errata/RHSA-2018:3527 https://access.redhat.com/errata/RHSA-2018:3528 https://access.redhat.com/errata/RHSA-2018:3529 https://access.redhat.com/errata/RHSA-2018:3595 https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-14627 https://issues.jboss.org/browse/WFLY-9107 https://security.netapp.com/advisory/ntap-20181221-0002 https://access.redhat.com/security/cve/CVE-2018-14627 https://bugzilla.redhat.com/show_bug.cgi?id=1624664 • CWE-319: Cleartext Transmission of Sensitive Information •
CVE-2018-10682
https://notcve.org/view.php?id=CVE-2018-10682
An issue was discovered in WildFly 10.1.2.Final. It is possible for an attacker to access the administration panel on TCP port 9990 without any authentication using "anonymous" access that is automatically created. Once logged in, a misconfiguration present by default (auto-deployment) permits an anonymous user to deploy a malicious .war file, leading to remote code execution. NOTE: the vendor indicates that anonymous access is not available in the default installation; however, it remains optional because there are several use cases for it, including development environments and network architectures that have a proxy server for access control to the WildFly server ** EN DISPUTA ** Se ha descubierto un problema en WildFly 10.1.2.Final. Es posible que un atacante acceda al panel de administración en el puerto TCP 9990 sin autenticación por medio del acceso "anonymous" que se crea automáticamente. • https://github.com/kmkz/exploit/blob/master/CVE-2018-10682-CVE-2018-10683.txt • CWE-287: Improper Authentication •
CVE-2018-10683
https://notcve.org/view.php?id=CVE-2018-10683
An issue was discovered in WildFly 10.1.2.Final. In the case of a default installation without a security realm reference, an attacker can successfully access the server without authentication. NOTE: the Security Realms documentation in the product's Admin Guide indicates that "without a security realm reference" implies "effectively unsecured." The vendor explicitly supports these unsecured configurations because they have valid use cases during development ** EN DISPUTA ** Se ha descubierto un problema en WildFly 10.1.2.Final. En el caso de una instalación por defecto sin una referencia de realm de seguridad, un atacante puede acceder con éxito al servidor sin autenticación. • https://github.com/kmkz/exploit/blob/master/CVE-2018-10682-CVE-2018-10683.txt • CWE-287: Improper Authentication •