Apache TomEE Security Vulnerabilities
This page lists the security vulnerabilities fixed in Apache TomEE releases. Each vulnerability is given a security impact rating by either the Apache TomEE team or by the dependent project supplying the fix - please note that this rating is not uniform and will vary from project to project. We also list the versions of Apache TomEE the flaw is known to affect, and where a flaw has not been verified list the version with a question mark.
| Only Apache TomEE 10.x and 11.x are maintained. End of life versions may be listed as affected, but they receive no fixes. See Supported versions. |
| Vulnerabilities that are not TomEE vulnerabilities but have either been incorrectly reported against TomEE or where TomEE provides a workaround are listed bellow in the section "Not a vulnerability". |
Please note that binary patches are never provided. If you need to apply a source code patch, use the building instructions for the Apache TomEE version that you are using. Instructions for building TomEE from source are available here.
If you need help on building or configuring TomEE or other help on following the instructions to mitigate the known vulnerabilities listed here, please send your questions to the public Users mailing list
If you have encountered an unlisted security vulnerability or other unexpected behaviour that has security impact, or if the descriptions here are incomplete, please report them privately to the Apache Security Team. Thank you.
Fixed in Apache TomEE 10.3.0 and 11.0.0-M2
The following vulnerabilities were announced on 10 November 2026. All of them are resolved in Apache TomEE 10.3.0 and Apache TomEE 11.0.0-M2. Several fixes change default behavior. See the TomEE 10.3.0 migration guide and the TomEE 11.0.0-M2 migration guide before upgrading.
Fixed vulnerabilities
| CVE | Severity | Title |
|---|---|---|
Important |
EJB method authorization is silently skipped on JDK 21+ |
|
Important |
Authorization bypass in MicroProfile JWT role checks for JAX-RS resources |
|
Important |
Well-known administrative credentials created at startup |
|
Important |
Authentication bypass with empty password in LDAP identity store |
|
Important |
Authentication bypass on EJB web service endpoints via HTTP method |
|
Moderate |
Path traversal via stateful EJB passivation |
|
Moderate |
Stateful session bean hijacking via predictable session identifiers |
|
Moderate |
Missing authorization on internal deployer EJBs in default profile |
|
Moderate |
Missing TLS hostname verification in ejbds client connections |
|
Moderate |
Derby network service listens on all interfaces |
|
Moderate |
Database credential disclosure via remote JNDI lookup |
|
Moderate |
Authentication bypass for accounts without a stored password in SQL login module |
|
Moderate |
Local code execution via predictable passivation files in the shared temporary directory |
|
Moderate |
Privilege escalation via leaked MicroProfile JWT run-as identity |
|
Moderate |
Privilege escalation via WS-Security caller identity leaking between requests |
|
Moderate |
Privilege escalation via user name matching a role name |
|
Moderate |
Unauthenticated server shutdown via the admin port |
|
Moderate |
Security constraint bypass via request routing |
|
Moderate |
Predictable HTTP session identifiers in embedded server |
|
Moderate |
LDAP injection in LDAP identity store |
|
Moderate |
Missing authentication on EJB web service endpoints deployed in a web application |
|
Low |
Username enumeration and timing side channel in JAAS login modules |
|
Low |
Expired MicroProfile JWT tokens accepted with negative clock skew |
|
Low |
Authentication with the stored password digest in Tomcat user identity store |
|
Low |
Unauthenticated LiveReload endpoint reachable from the network |
|
Low |
Predictable OpenID Connect state and nonce values |
Vulnerabilities in removed modules
The following vulnerabilities affect optional modules that are no longer part of TomEE 10.3.0 and 11.0.0-M2:
the embedded OpenEJB HTTP server (openejb-http) and the endpoints it published, the Hessian remoting module
(openejb-hessian), and the SSH administration shell (openejb-ssh, openejb-common-cli). No fixed version of these
modules exists. Upgrading to TomEE 10.3.0 or 11.0.0-M2 removes them. If you cannot upgrade, block network access to these
services from untrusted clients or stop using them.
| CVE | Severity | Title |
|---|---|---|
Moderate |
DoS via unbounded request body and multipart handling in embedded HTTP server |
|
Moderate |
Missing authentication for Hessian endpoints in embedded HTTP server |
|
Moderate |
Authentication bypass of Hessian EJB endpoints due to ignored security settings |
|
Moderate |
Authentication bypass for Hessian endpoints in non-root web applications |
|
Moderate |
Authentication bypass in the embedded HTTP server for endpoints protected by HTTP Basic authentication |
|
Moderate |
Path traversal in embedded HTTP server static resource handling |
|
Moderate |
Caller identity leaks across requests in embedded HTTP server |
|
Moderate |
Code execution by any authenticated user via the SSH administration shell |
|
Moderate |
Authentication bypass via programmatic authentication in embedded HTTP server |
|
Moderate |
Missing authentication for web service endpoints in embedded HTTP server |
|
Low |
Session fixation in embedded HTTP server |
|
Low |
HTTP sessions shared across web applications in embedded HTTP server |
Details
Important: EJB method authorization is silently skipped on JDK 21+
Apache TomEE running on JDK 21 or later skips EJB method authorization checks, allowing callers to invoke EJB methods without the configured access restrictions being enforced.
Affected versions:
-
org.apache.tomee:openejb-core10.1.1 before 10.3.0 -
org.apache.tomee:openejb-core11.0.0-M1 before 11.0.0-M2
Credit: The Apache Software Foundation (finder), Claude Security (tool), Markus Jung (remediation developer)
Important: Authorization bypass in MicroProfile JWT role checks for JAX-RS resources
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, resource classes that inherit the same method from a common superclass share their constraints, and class-level constraints declared on a superclass are ignored. A remote attacker can invoke resources that should be denied to them, in some configurations without authentication.
Affected versions:
-
org.apache.tomee:mp-jwt7.1.0 before 10.0.0-M1 -
org.apache.tomee:mp-jwt10.0.0-M1 before 10.3.0 -
org.apache.tomee:mp-jwt11.0.0-M1 before 11.0.0-M2
Credit: The Apache Software Foundation (finder), Claude Security (tool), Richard Zowalla (remediation developer)
Important: Well-known administrative credentials created at startup
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. A remote attacker can use these credentials to authenticate to web applications that use the default realm and grant access to any authenticated user or to the TomEE administrative role.
Affected versions:
-
org.apache.openejb:tomee-catalina1.5.1 through 1.7.5 -
org.apache.tomee:tomee-catalina7.0.0-M1 before 10.0.0-M1 -
org.apache.tomee:tomee-catalina10.0.0-M1 before 10.3.0 -
org.apache.tomee:tomee-catalina11.0.0-M1 before 11.0.0-M2
Credit: The Apache Software Foundation (finder), Claude Security (tool), Markus Jung (remediation developer)
Important: Authentication bypass with empty password in LDAP identity store
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. A remote attacker can then authenticate as any existing user without knowing the password.
Affected versions:
-
org.apache.tomee:tomee-security8.0.4 before 10.0.0-M1 -
org.apache.tomee:tomee-security10.0.0-M1 before 10.3.0 -
org.apache.tomee:tomee-security11.0.0-M1 before 11.0.0-M2
Credit: The Apache Software Foundation (finder), Claude Security (tool), Markus Jung (remediation developer)
Important: Authentication bypass on EJB web service endpoints via HTTP method
The security constraint generated for EJB JAX-WS endpoints with configured authentication protects only some HTTP methods. A remote unauthenticated attacker can bypass authentication by sending requests with another HTTP method.
Affected versions:
-
org.apache.openejb:tomee-webservices4.0.0-beta-1 through 4.0.0 -
org.apache.openejb:tomee-webservices1.5.0 through 1.7.5 -
org.apache.tomee:tomee-webservices7.0.0-M1 before 10.0.0-M1 -
org.apache.tomee:tomee-webservices10.0.0-M1 before 10.3.0 -
org.apache.tomee:tomee-webservices11.0.0-M1 before 11.0.0-M2
Credit: The Apache Software Foundation (finder), Claude Security (tool), Jonathan Gallimore (remediation developer)
Moderate: Path traversal via stateful EJB passivation
The stateful session bean passivation mechanism derives the on-disk file name from a client-supplied identifier without validating it. A remote attacker with access to the remote EJB service can cause session state to be read from or written to files outside the passivation directory.
Affected versions:
-
org.apache.openejb:openejb-core4.0.0-beta-1 through 4.7.5 -
org.apache.tomee:openejb-core7.0.0-M1 before 10.0.0-M1 -
org.apache.tomee:openejb-core10.0.0-M1 before 10.3.0 -
org.apache.tomee:openejb-core11.0.0-M1 before 11.0.0-M2
Credit: The Apache Software Foundation (finder), Claude Security (tool), Markus Jung (remediation developer)
Moderate: Stateful session bean hijacking via predictable session identifiers
Stateful session bean identifiers are not generated from a cryptographically secure random source. A remote attacker with access to the EJB remote endpoint who holds one valid identifier can derive those of other clients' sessions and invoke methods on their beans, exposing or modifying other users' session state.
Affected versions:
-
org.apache.openejb:openejb-core4.0.0-beta-1 through 4.7.5 -
org.apache.tomee:openejb-core7.0.0-M1 before 10.0.0-M1 -
org.apache.tomee:openejb-core10.0.0-M1 before 10.3.0 -
org.apache.tomee:openejb-core11.0.0-M1 before 11.0.0-M2
Credit: The Apache Software Foundation (finder), Claude Security (tool), Markus Jung (remediation developer)
Moderate: Missing authorization on internal deployer EJBs in default profile
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. A remote unauthenticated attacker able to reach the remote EJB endpoint could deploy arbitrary applications and execute code. Only installations that enabled the system applications and a remote EJB endpoint are exposed.
Affected versions:
-
org.apache.openejb:openejb-core4.5.1 through 4.7.5 -
org.apache.tomee:openejb-core7.0.0-M1 before 10.0.0-M1 -
org.apache.tomee:openejb-core10.0.0-M1 before 10.3.0 -
org.apache.tomee:openejb-core11.0.0-M1 before 11.0.0-M2
Credit: The Apache Software Foundation (finder), Claude Security (tool), Markus Jung (remediation developer)
Moderate: Missing TLS hostname verification in ejbds client connections
The remote EJB client does not verify that the hostname of the server it connects to matches the server’s TLS certificate. An attacker able to intercept network traffic between an EJB client and server can impersonate the server and read or modify the traffic, including credentials and invocation data.
Affected versions:
-
org.apache.openejb:openejb-client4.0.0-beta-1 through 4.7.5 -
org.apache.tomee:openejb-client7.0.0-M1 before 10.0.0-M1 -
org.apache.tomee:openejb-client10.0.0-M1 before 10.3.0 -
org.apache.tomee:openejb-client11.0.0-M1 before 11.0.0-M2
Credit: The Apache Software Foundation (finder), Claude Security (tool), Markus Jung (remediation developer)
Moderate: Derby network service listens on all interfaces
The embedded Derby network service ignores its configured bind address and listens on all network interfaces. When the service is enabled, a remote attacker with network access can connect to the database server and read or modify data.
Affected versions:
-
org.apache.openejb:openejb-derbynet4.0.0-beta-1 through 4.7.5 -
org.apache.tomee:openejb-derbynet7.0.0-M1 before 10.0.0-M1 -
org.apache.tomee:openejb-derbynet10.0.0-M1 before 10.3.0 -
org.apache.tomee:openejb-derbynet11.0.0-M1 before 11.0.0-M2
Credit: The Apache Software Foundation (finder), Claude Security (tool), Markus Jung (remediation developer)
Moderate: Database credential disclosure via remote JNDI lookup
The EJBd remote protocol returns datasource connection details, including database credentials, to remote clients that look up a datasource. A remote client able to reach the EJBd endpoint can obtain the database credentials and connect to the database directly.
Affected versions:
-
org.apache.openejb:openejb-ejbd4.0.0-beta-1 through 4.7.5 -
org.apache.tomee:openejb-ejbd7.0.0-M1 before 10.0.0-M1 -
org.apache.tomee:openejb-ejbd10.0.0-M1 before 10.3.0 -
org.apache.tomee:openejb-ejbd11.0.0-M1 before 11.0.0-M2
Credit: The Apache Software Foundation (finder), Claude Security (tool), Markus Jung (remediation developer)
Moderate: Authentication bypass for accounts without a stored password in SQL login module
The JDBC based JAAS login module accepts a login without a password for accounts whose stored password is NULL. A remote attacker who knows the user name of such an account can authenticate as that user and obtain its roles. Only deployments using this login module with NULL passwords in the user table are affected.
Affected versions:
-
org.apache.openejb:openejb-core4.0.0-beta-1 through 4.7.5 -
org.apache.tomee:openejb-core7.0.0-M1 before 10.0.0-M1 -
org.apache.tomee:openejb-core10.0.0-M1 before 10.3.0 -
org.apache.tomee:openejb-core11.0.0-M1 before 11.0.0-M2
Credit: The Apache Software Foundation (finder), Claude Security (tool), Richard Zowalla (remediation developer)
Moderate: Local code execution via predictable passivation files in the shared temporary directory
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, and is deserialized on activation. A local attacker who can write to that directory can read passivated session state or supply data that the server deserializes, potentially leading to code execution as the server process.
Affected versions:
-
org.apache.openejb:openejb-core4.0.0-beta-1 through 4.7.5 -
org.apache.tomee:openejb-core7.0.0-M1 before 10.0.0-M1 -
org.apache.tomee:openejb-core10.0.0-M1 before 10.3.0 -
org.apache.tomee:openejb-core11.0.0-M1 before 11.0.0-M2
Credit: The Apache Software Foundation (finder), Claude Security (tool), Richard Zowalla (remediation developer)
Moderate: Privilege escalation via leaked MicroProfile JWT run-as identity
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 normally. A remote attacker holding a valid token can cause later, unrelated requests served by the same thread to invoke enterprise beans with the elevated run-as identity.
Affected versions:
-
org.apache.tomee:mp-jwt8.0.0-M2 before 10.0.0-M1 -
org.apache.tomee:mp-jwt10.0.0-M1 before 10.3.0 -
org.apache.tomee:mp-jwt11.0.0-M1 before 11.0.0-M2
Credit: The Apache Software Foundation (finder), Claude Security (tool), Richard Zowalla (remediation developer)
Moderate: Privilege escalation via WS-Security caller identity leaking between requests
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. A remote unauthenticated attacker whose request is later processed on the same thread can invoke protected EJB methods with the identity of a previously authenticated user.
Affected versions:
-
org.apache.openejb:openejb-cxf4.0.0-beta-1 through 4.7.5 -
org.apache.tomee:openejb-cxf7.0.0-M1 before 10.0.0-M1 -
org.apache.tomee:openejb-cxf10.0.0-M1 before 10.3.0 -
org.apache.tomee:openejb-cxf11.0.0-M1 before 11.0.0-M2
Credit: The Apache Software Foundation (finder), Claude Security (tool), Richard Zowalla (remediation developer)
Moderate: Privilege escalation via user name matching a role name
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. An authenticated attacker who can obtain an account whose user name equals a role name, for example through self-registration, is granted that role wherever authorization is evaluated through the Jakarta Authorization policy.
Affected versions:
-
org.apache.tomee:tomee-catalina8.0.7 before 10.0.0-M1 -
org.apache.tomee:tomee-catalina10.0.0-M1 before 10.3.0 -
org.apache.tomee:tomee-catalina11.0.0-M1 before 11.0.0-M2
Credit: The Apache Software Foundation (finder), Claude Security (tool), Richard Zowalla (remediation developer)
Moderate: Unauthenticated server shutdown via the admin port
The admin service of the standalone OpenEJB server accepts stop requests without any authentication. Any local user or process able to connect to the admin port can stop the server, leading to denial of service; the admin service is enabled by default in the standalone server and bound to the loopback interface.
Affected versions:
-
org.apache.openejb:openejb-server4.0.0-beta-1 through 4.7.5 -
org.apache.tomee:openejb-server7.0.0-M1 before 10.0.0-M1 -
org.apache.tomee:openejb-server10.0.0-M1 before 10.3.0 -
org.apache.tomee:openejb-server11.0.0-M1 before 11.0.0-M2
Credit: The Apache Software Foundation (finder), Claude Security (tool), Richard Zowalla (remediation developer)
Moderate: Security constraint bypass via request routing
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. If a route copies client-controlled parts of the request path into its destination, a remote attacker can reach protected resources or read application configuration and class files. Only installations with such a routing configuration are affected.
Affected versions:
-
org.apache.openejb:tomee-catalina1.5.0 through 1.7.5 -
org.apache.tomee:tomee-catalina7.0.0-M1 before 10.0.0-M1 -
org.apache.tomee:tomee-catalina10.0.0-M1 before 10.3.0 -
org.apache.tomee:tomee-catalina11.0.0-M1 before 11.0.0-M2
Credit: The Apache Software Foundation (finder), Claude Security (tool), Markus Jung (remediation developer)
Moderate: Predictable HTTP session identifiers in embedded server
The embedded server generates HTTP session identifiers with a non-cryptographic random number generator by default. A remote attacker who observes a session identifier can predict the identifiers issued to other users and hijack their sessions, if the application relies on HTTP sessions for authentication.
Affected versions:
-
org.apache.tomee:tomee-embedded7.0.0-M1 before 10.0.0-M1 -
org.apache.tomee:tomee-embedded10.0.0-M1 before 10.3.0 -
org.apache.tomee:tomee-embedded11.0.0-M1 before 11.0.0-M2
Credit: The Apache Software Foundation (finder), Claude Security (tool), Markus Jung (remediation developer)
Moderate: LDAP injection in LDAP identity store
The Jakarta Security LDAP identity store does not neutralize special characters in the caller name before using it in directory queries. A remote unauthenticated attacker can alter the queries to enumerate accounts, infer directory attribute values, or influence which directory entry the login is validated against. Only applications using the LDAP identity store are affected.
Affected versions:
-
org.apache.tomee:tomee-security8.0.4 before 10.0.0-M1 -
org.apache.tomee:tomee-security10.0.0-M1 before 10.3.0 -
org.apache.tomee:tomee-security11.0.0-M1 before 11.0.0-M2
Credit: The Apache Software Foundation (finder), Claude Security (tool), Markus Jung (remediation developer)
Moderate: Missing authentication on EJB web service endpoints deployed in a web application
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. A remote unauthenticated attacker can invoke the web service operations, unless the application protects the endpoint with its own web.xml security constraints or EJB method permissions.
Affected versions:
-
org.apache.openejb:tomee-webservices4.0.0-beta-1 through 4.0.0 -
org.apache.openejb:tomee-webservices1.5.0 through 1.7.5 -
org.apache.tomee:tomee-webservices7.0.0-M1 before 10.0.0-M1 -
org.apache.tomee:tomee-webservices10.0.0-M1 before 10.3.0 -
org.apache.tomee:tomee-webservices11.0.0-M1 before 11.0.0-M2
Credit: The Apache Software Foundation (finder), Claude Security (tool), Jonathan Gallimore (remediation developer)
Low: Username enumeration and timing side channel in JAAS login modules
The bundled JAAS login modules leak whether a username exists and compare credentials in a non-constant-time manner. A remote unauthenticated attacker can enumerate valid accounts and may infer credential material through timing analysis.
Affected versions:
-
org.apache.openejb:openejb-core4.0.0-beta-1 through 4.7.5 -
org.apache.tomee:openejb-core7.0.0-M1 before 10.0.0-M1 -
org.apache.tomee:openejb-core10.0.0-M1 before 10.3.0 -
org.apache.tomee:openejb-core11.0.0-M1 before 11.0.0-M2
Credit: The Apache Software Foundation (finder), Claude Security (tool), Markus Jung (remediation developer)
Low: Expired MicroProfile JWT tokens accepted with negative clock skew
A negative MicroProfile JWT clock skew setting is not rejected and disables validation of the token expiration and other time-based claims. In such configurations, an attacker in possession of an expired token can still authenticate with it.
Affected versions:
-
org.apache.tomee:mp-jwt10.0.0-M1 before 10.3.0 -
org.apache.tomee:mp-jwt11.0.0-M1 before 11.0.0-M2
Credit: The Apache Software Foundation (finder), Claude Security (tool), Richard Zowalla (remediation developer)
Low: Authentication with the stored password digest in Tomcat user identity store
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. When digested passwords are stored, an attacker who obtained a stored digest, for example from a leaked users file or backup, can authenticate with the digest instead of the password.
Affected versions:
-
org.apache.tomee:tomee-security8.0.0-M2 before 10.0.0-M1 -
org.apache.tomee:tomee-security10.0.0-M1 before 10.3.0 -
org.apache.tomee:tomee-security11.0.0-M1 before 11.0.0-M2
Credit: The Apache Software Foundation (finder), Claude Security (tool), Richard Zowalla (remediation developer)
Low: Unauthenticated LiveReload endpoint reachable from the network
The development-time LiveReload support listens on all network interfaces without authentication and accepts websocket connections from any origin. A network attacker, or a web page visited by the developer, can observe the names of changed files in the watched folder and the server version, and reach the deployed applications through the additional port. This only affects LiveReload enabled in the embedded Maven plugin.
Affected versions:
-
org.apache.tomee:livereload-tomee7.0.0-M2 before 10.0.0-M1 -
org.apache.tomee:livereload-tomee10.0.0-M1 before 10.3.0 -
org.apache.tomee:livereload-tomee11.0.0-M1 before 11.0.0-M2
Credit: The Apache Software Foundation (finder), Claude Security (tool), Richard Zowalla (remediation developer)
Low: Predictable OpenID Connect state and nonce values
The Jakarta Security OpenID Connect authentication mechanism generates the state and nonce values with a non-cryptographic random number generator and insufficient entropy. A remote attacker who predicts these values can forge an authentication callback that logs a victim into the attacker’s account, and the replay protection for ID tokens is weakened.
Affected versions:
-
org.apache.tomee:tomee-security10.0.0-M2 before 10.3.0 -
org.apache.tomee:tomee-security11.0.0-M1 before 11.0.0-M2
Credit: The Apache Software Foundation (finder), Claude Security (tool), Markus Jung (remediation developer)
Moderate: DoS via unbounded request body and multipart handling in embedded HTTP server
The embedded OpenEJB HTTP server does not limit the size of incoming request bodies or of multipart requests, and does not remove the temporary files it creates for multipart parts. A remote unauthenticated attacker can cause excessive memory or disk usage, leading to denial of service. Deployments using the Tomcat connectors are not affected. Users are recommended to block network access to the embedded HTTP server from untrusted clients, or to migrate to the Tomcat based TomEE distributions.
Affected versions:
-
org.apache.openejb:openejb-http4.0.0-beta-1 through 4.7.5 -
org.apache.tomee:openejb-http7.0.0-M1 before 10.0.0-M1 -
org.apache.tomee:openejb-http10.0.0-M1 through 10.2.0 -
org.apache.tomee:openejb-http11.0.0-M1
Credit: The Apache Software Foundation (finder), Claude Security (tool), Markus Jung (remediation developer)
Moderate: Missing authentication for Hessian endpoints in embedded HTTP server
When Hessian remoting endpoints are served by the embedded HTTP server, configured authentication and transport security requirements are silently ignored. A remote unauthenticated attacker can invoke the exposed EJB methods without credentials or over an unencrypted connection. Only deployments that use the embedded HTTP server rather than Tomcat and rely on these settings are affected. Users are recommended to block network access to Hessian endpoints from untrusted clients, or to migrate to another remoting protocol.
Affected versions:
-
org.apache.openejb:openejb-hessian4.6.0 through 4.7.5 -
org.apache.tomee:openejb-hessian7.0.0-M1 before 10.0.0-M1 -
org.apache.tomee:openejb-hessian10.0.0-M1 through 10.2.0 -
org.apache.tomee:openejb-hessian11.0.0-M1
Credit: The Apache Software Foundation (finder), Claude Security (tool), Markus Jung (remediation developer)
Moderate: Authentication bypass of Hessian EJB endpoints due to ignored security settings
When an EJB is exposed over the optional Hessian protocol inside an existing web application, some configured authentication and transport security settings are silently not enforced. A remote unauthenticated attacker can invoke the exposed EJB methods. Only deployments using the Hessian module with such settings are affected. Users are recommended to block network access to Hessian endpoints from untrusted clients, or to migrate to another remoting protocol.
Affected versions:
-
org.apache.openejb:openejb-hessian4.6.0 through 4.7.5 -
org.apache.tomee:openejb-hessian7.0.0-M1 before 10.0.0-M1 -
org.apache.tomee:openejb-hessian10.0.0-M1 through 10.2.0 -
org.apache.tomee:openejb-hessian11.0.0-M1
Credit: The Apache Software Foundation (finder), Claude Security (tool), Markus Jung (remediation developer)
Moderate: Authentication bypass for Hessian endpoints in non-root web applications
When Hessian remoting is configured with BASIC authentication, the authentication check is not applied to Hessian endpoints of applications deployed under a non-root context path. A remote unauthenticated attacker can invoke the exposed EJB methods without credentials. Users are recommended to block network access to Hessian endpoints from untrusted clients, or to migrate to another remoting protocol.
Affected versions:
-
org.apache.openejb:openejb-hessian4.6.0 through 4.7.5 -
org.apache.tomee:openejb-hessian7.0.0-M1 before 10.0.0-M1 -
org.apache.tomee:openejb-hessian10.0.0-M1 through 10.2.0 -
org.apache.tomee:openejb-hessian11.0.0-M1
Credit: The Apache Software Foundation (finder), Claude Security (tool), Markus Jung (remediation developer)
Moderate: Authentication bypass in the embedded HTTP server for endpoints protected by HTTP Basic authentication
The embedded OpenEJB HTTP server dispatches some requests to REST endpoints configured for HTTP Basic authentication without verifying credentials. A remote unauthenticated attacker can invoke protected resources, bypassing authentication. Only deployments that use the embedded HTTP server with Basic authentication are affected. Users are recommended to block network access to the embedded HTTP server from untrusted clients, or to migrate to the Tomcat based TomEE distributions.
Affected versions:
-
org.apache.openejb:openejb-http4.0.0-beta-1 through 4.7.5 -
org.apache.tomee:openejb-http7.0.0-M1 before 10.0.0-M1 -
org.apache.tomee:openejb-http10.0.0-M1 through 10.2.0 -
org.apache.tomee:openejb-http11.0.0-M1
Credit: The Apache Software Foundation (finder), Claude Security (tool), Markus Jung (remediation developer)
Moderate: Path traversal in embedded HTTP server static resource handling
The embedded OpenEJB HTTP server does not restrict static resource paths to the configured resource directories. A remote unauthenticated attacker can read arbitrary files accessible to the server process. Users are recommended to block network access to the embedded HTTP server from untrusted clients, or to migrate to the Tomcat based TomEE distributions.
Affected versions:
-
org.apache.tomee:openejb-http7.0.0-M1 before 10.0.0-M1 -
org.apache.tomee:openejb-http10.0.0-M1 through 10.2.0 -
org.apache.tomee:openejb-http11.0.0-M1
Credit: The Apache Software Foundation (finder), Claude Security (tool), Markus Jung (remediation developer)
Moderate: Caller identity leaks across requests in embedded HTTP server
The embedded HTTP server does not clear the security identity established during a request before its worker thread handles the next request. A remote unauthenticated attacker can have their request processed with the identity of a previously authenticated user, gaining that user’s privileges. Only applications served by the embedded HTTP server that authenticate programmatically or via basic authentication are affected. Users are recommended to block network access to the embedded HTTP server from untrusted clients, or to migrate to the Tomcat based TomEE distributions.
Affected versions:
-
org.apache.tomee:openejb-http7.0.0-M1 before 10.0.0-M1 -
org.apache.tomee:openejb-http10.0.0-M1 through 10.2.0 -
org.apache.tomee:openejb-http11.0.0-M1
Credit: The Apache Software Foundation (finder), Claude Security (tool), Markus Jung (remediation developer)
Moderate: Code execution by any authenticated user via the SSH administration shell
The optional SSH administration service grants full access to the administration shell to every user that authenticates against its configured login domain, without checking for an administrative role. An attacker holding the credentials of any user in that domain, including a low-privileged application user, can execute arbitrary code as the server process. Users are recommended to disable the SSH administration service, or to block network access to it from untrusted clients and restrict its login domain to administrative users.
Affected versions:
-
org.apache.openejb:openejb-ssh4.0.0 through 4.7.5 -
org.apache.tomee:openejb-ssh7.0.0-M1 before 10.0.0-M1 -
org.apache.tomee:openejb-ssh10.0.0-M1 through 10.2.0 -
org.apache.tomee:openejb-ssh11.0.0-M1 -
org.apache.openejb:openejb-common-cli4.0.0 through 4.7.5 -
org.apache.tomee:openejb-common-cli7.0.0-M1 before 10.0.0-M1 -
org.apache.tomee:openejb-common-cli10.0.0-M1 through 10.2.0 -
org.apache.tomee:openejb-common-cli11.0.0-M1
Credit: The Apache Software Foundation (finder), Claude Security (tool), Richard Zowalla (remediation developer)
Moderate: Authentication bypass via programmatic authentication in embedded HTTP server
The embedded OpenEJB HTTP server reports every request as authenticated when an application requests authentication programmatically. A remote unauthenticated attacker can access functionality protected this way. Only applications served by the embedded HTTP server that rely on programmatic authentication are affected. Users are recommended to block network access to the embedded HTTP server from untrusted clients, or to migrate to the Tomcat based TomEE distributions.
Affected versions:
-
org.apache.openejb:openejb-http4.0.0-beta-1 through 4.7.5 -
org.apache.tomee:openejb-http7.0.0-M1 before 10.0.0-M1 -
org.apache.tomee:openejb-http10.0.0-M1 through 10.2.0 -
org.apache.tomee:openejb-http11.0.0-M1
Credit: The Apache Software Foundation (finder), Claude Security (tool), Richard Zowalla (remediation developer)
Moderate: Missing authentication for web service endpoints in embedded HTTP server
When JAX-WS or JAX-RS endpoints are published by the embedded OpenEJB HTTP server rather than Tomcat, some configured authentication methods are silently ignored and the endpoint is published without authentication. A remote unauthenticated attacker can invoke the exposed operations without credentials. Only deployments that use the embedded HTTP server and rely on such an authentication method are affected. Users are recommended to block network access to the embedded HTTP server from untrusted clients, or to migrate to the Tomcat based TomEE distributions.
Affected versions:
-
org.apache.openejb:openejb-webservices4.0.0-beta-1 through 4.7.5 -
org.apache.openejb:openejb-rest4.6.0 through 4.7.5 -
org.apache.tomee:openejb-webservices7.0.0-M1 before 10.0.0-M1 -
org.apache.tomee:openejb-webservices10.0.0-M1 through 10.2.0 -
org.apache.tomee:openejb-webservices11.0.0-M1 -
org.apache.tomee:openejb-rest7.0.0-M1 before 10.0.0-M1 -
org.apache.tomee:openejb-rest10.0.0-M1 through 10.2.0 -
org.apache.tomee:openejb-rest11.0.0-M1
Credit: The Apache Software Foundation (finder), Claude Security (tool), Markus Jung (remediation developer)
Low: Session fixation in embedded HTTP server
The embedded HTTP server does not invalidate the previous session identifier when an application changes the session id, e.g. after login. An attacker who can plant a session identifier in a victim’s browser can hijack the victim’s authenticated session. Users are recommended to block network access to the embedded HTTP server from untrusted clients, or to migrate to the Tomcat based TomEE distributions.
Affected versions:
-
org.apache.tomee:openejb-http7.0.0-M1 before 10.0.0-M1 -
org.apache.tomee:openejb-http10.0.0-M1 through 10.2.0 -
org.apache.tomee:openejb-http11.0.0-M1
Credit: The Apache Software Foundation (finder), Claude Security (tool), Markus Jung (remediation developer)
Low: HTTP sessions shared across web applications in embedded HTTP server
The embedded OpenEJB HTTP server does not isolate HTTP sessions between web applications. A remote attacker can use a session established in one web application in another one, which then trusts session state set by the first application. Only deployments hosting several web applications on the embedded HTTP server are affected. Users are recommended to block network access to the embedded HTTP server from untrusted clients, or to migrate to the Tomcat based TomEE distributions.
Affected versions:
-
org.apache.openejb:openejb-http4.5.2 through 4.7.5 -
org.apache.tomee:openejb-http7.0.0-M1 before 10.0.0-M1 -
org.apache.tomee:openejb-http10.0.0-M1 through 10.2.0 -
org.apache.tomee:openejb-http11.0.0-M1
Credit: The Apache Software Foundation (finder), Claude Security (tool), Richard Zowalla (remediation developer)
Fixed in Apache TomEE 7.0.1
-
3C45A20804-ABFF-4FED-A297-69AC95AB9A3F@apache.org%3E">CVE-2016-3092 Apache Tomcat Denial of Service
Fixed in Apache TomEE 7.0.0-M3 and 1.7.4
TomEE was subject until versions 1.7.3 and 7.0.0-M1 included to the 0-day vulnerability. Note that even if fixed in 7.0.0-M2 we recommand you to upgrade to the 7.0.0-M3 which includes a better fix for that (better defaults).
This issue only affects you if you rely on EJBd protocol (proprietary remote EJB protocol). This one one is not activated by default on the 7.x series but it was on the 1.x ones.
The related CVE numbers are:
-
CVE-2016-0779: The EJBd protocol provided by TomEE can exploit the 0-day vulnerability.
-
CVE-2015-8581: The EjbObjectInputStream class in Apache TomEE allows remote attackers to execute arbitrary commands via a serialized Java stream.
This has been fixed in commit 58cdbbef9c77ab2b44870f9d606593b49cde76d9.
Check properties configuration and Ejbd transport for more details (tomee.serialization.class.* and tomee.remote.support).
Credit
We would like to thank cpnrodzc7 who discovered it working with HP’s Zero Day Initiative
Fixed in Third-party
Covered by Apache TomEE 1.6.0.2
-
CVE-2014-0109: HTML content posted to SOAP endpoint could cause OOM errors
-
CVE-2014-0110: Large invalid content could cause temporary space to fill
-
CVE-2014-0034: The SecurityTokenService accepts certain invalid SAML Tokens as valid
-
CVE-2014-0035: UsernameTokens are sent in plaintext with a Symmetric EncryptBeforeSigning policy
Covered by Apache TomEE 1.6.0.1
-
Fixed in Tomcat 7.0.52 Important: Denial of Service CVE-2014-0050
Covered by Apache TomEE 1.6.0
-
CVE-2013-2160 - Denial of Service Attacks on Apache CXF
-
Note on CVE-2012-5575 - XML Encryption backwards compatibility attack on Apache CXF.
-
CVE-2013-0239 - Authentication bypass in the case of WS-SecurityPolicy enabled plaintext UsernameTokens.