Missing TLS hostname verification in Apache TomEE EJB client
The remote EJB client does not verify that the hostname of the server it connects to matches the server's TLS certificate.
23 records
The remote EJB client does not verify that the hostname of the server it connects to matches the server's TLS certificate.
The embedded Derby network service ignores its configured bind address and listens on all network interfaces.
The EJBd remote protocol returns datasource connection details, including database credentials, to remote clients that look up a datasource.
The JDBC based JAAS login module accepts a login without a password for accounts whose stored password is NULL.
When a non-default stateful session bean passivation strategy is configured, passivated bean state is written to predictably named files in the shared system temporary directory, reusing files that already exist there, a…
When MicroProfile JWT authentication is used for servlets that declare a run-as identity, the security state established for a request is not always cleared from the processing thread when the request does not complete n…
When MicroProfile JWT role-based access control is used, the access constraints of JAX-RS resources are not always enforced as declared: resources that declare an empty set of allowed roles are accessible to every caller…
After a successful WS-Security UsernameToken authentication, the caller identity stays associated with the worker thread once the request completes when web services are served by the standalone OpenEJB HTTP server.
When resolving security roles of a realm-authenticated caller, the caller's user name is also treated as a role name in addition to the roles assigned by the realm.
The Jakarta Security identity store backed by the Tomcat user database compares the supplied password with the stored value as plain text and ignores the configured credential handler.
The development-time LiveReload support listens on all network interfaces without authentication and accepts websocket connections from any origin.
The admin service of the standalone OpenEJB server accepts stop requests without any authentication.
With the default configuration and no users defined in the default user database, TomEE silently adds an administrative user with a well-known password at startup.
The optional request routing feature forwards requests to their configured destination without applying the security constraints of that destination or the protection of the web application's private directories.
The embedded server generates HTTP session identifiers with a non-cryptographic random number generator by default.
The Jakarta Security LDAP identity store accepts an empty password as valid if the directory server allows unauthenticated binds, which some directory servers do by default.
The Jakarta Security LDAP identity store does not neutralize special characters in the caller name before using it in directory queries.
Authentication configured for an EJB JAX-WS endpoint in the TomEE deployment descriptor is not enforced when the endpoint is published within an existing web application.
The security constraint generated for EJB JAX-WS endpoints with configured authentication protects only some HTTP methods.
The internal system EJBs used for remote deployment and configuration did not enforce their administrative role check when the server ran with the default profile.
Stateful session bean identifiers are not generated from a cryptographically secure random source.
The stateful session bean passivation mechanism derives the on-disk file name from a client-supplied identifier without validating it.
The bundled JAAS login modules leak whether a username exists and compare credentials in a non-constant-time manner.