Eclipse Jersey 2.28 to 2.33 and Eclipse Jersey 3.0.0 to 3.0.1 contains a local information disclosure vulnerability. This is due to the use of the File.createTempFile which creates a file inside of the system temporary directory with the permissions: -rw-r–r–. Thus the contents of this file are viewable by all other users locally on the system. As such, if the contents written is security sensitive, it can be disclosed to other local users.
The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Jersey | Eclipse | 2.28 (including) | 2.34 (excluding) |
| Jersey | Eclipse | 3.0.0 (including) | 3.0.2 (excluding) |
| Red Hat AMQ Streams 1.8.0 | RedHat | jersey-common | * |
| RHINT Camel-K 1.6.4 | RedHat | jersey-common | * |
| RHINT Camel-Q 2.2.1 | RedHat | jersey-common | * |
| Jersey1 | Ubuntu | trusty | * |
| Jersey1 | Ubuntu | upstream | * |
Resources such as files and directories may be inadvertently exposed through mechanisms such as insecure permissions, or when a program accidentally operates on the wrong object. For example, a program may intend that private files can only be provided to a specific user. This effectively defines a control sphere that is intended to prevent attackers from accessing these private files. If the file permissions are insecure, then parties other than the user will be able to access those files. A separate control sphere might effectively require that the user can only access the private files, but not any other files on the system. If the program does not ensure that the user is only requesting private files, then the user might be able to access other files on the system. In either case, the end result is that a resource has been exposed to the wrong party.