A flaw was found in RESTEasy, where an incorrect response to an HTTP request is provided. This flaw allows an attacker to gain access to privileged information. The highest threat from this vulnerability is to confidentiality and integrity. Versions before resteasy 2.0.0.Alpha3 are affected.
The product does not properly synchronize shared data, such as static variables across threads, which can lead to undefined behavior and unpredictable data changes.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Resteasy | Redhat | * | 2.0.0 (excluding) |
| Resteasy | Redhat | 2.0.0-alpha1 (including) | 2.0.0-alpha1 (including) |
| Resteasy | Redhat | 2.0.0-alpha2 (including) | 2.0.0-alpha2 (including) |
| Text-Only RHOAR | RedHat | resteasy | * |
| Resteasy | Ubuntu | groovy | * |
| Resteasy | Ubuntu | hirsute | * |
| Resteasy | Ubuntu | impish | * |
| Resteasy | Ubuntu | kinetic | * |
| Resteasy | Ubuntu | lunar | * |
| Resteasy | Ubuntu | mantic | * |
| Resteasy | Ubuntu | trusty | * |
| Resteasy | Ubuntu | xenial | * |
| Resteasy3.0 | Ubuntu | bionic | * |
| Resteasy3.0 | Ubuntu | groovy | * |
| Resteasy3.0 | Ubuntu | hirsute | * |
| Resteasy3.0 | Ubuntu | impish | * |
| Resteasy3.0 | Ubuntu | kinetic | * |
| Resteasy3.0 | Ubuntu | lunar | * |
| Resteasy3.0 | Ubuntu | mantic | * |
| Resteasy3.0 | Ubuntu | trusty | * |
Within servlets, shared static variables are not protected from concurrent access, but servlets are multithreaded. This is a typical programming mistake in J2EE applications, since the multithreading is handled by the framework. When a shared variable can be influenced by an attacker, one thread could wind up modifying the variable to contain data that is not valid for a different thread that is also using the data within the variable. Note that this weakness is not unique to servlets.