Potential leak of left-over heap data if custom error page templates containing special non-standard variables are used. Tinyproxy commit 84f203f and earlier use uninitialized buffers in process_request() function.
The product initializes or sets a resource with a default that is intended to be changed by the administrator, but the default is not secure.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Tinyproxy | Tinyproxy_project | * | 1.11.1 (including) |
| Tinyproxy | Ubuntu | bionic | * |
| Tinyproxy | Ubuntu | esm-apps/bionic | * |
| Tinyproxy | Ubuntu | esm-apps/jammy | * |
| Tinyproxy | Ubuntu | esm-apps/xenial | * |
| Tinyproxy | Ubuntu | focal | * |
| Tinyproxy | Ubuntu | kinetic | * |
| Tinyproxy | Ubuntu | lunar | * |
| Tinyproxy | Ubuntu | mantic | * |
| Tinyproxy | Ubuntu | trusty | * |
| Tinyproxy | Ubuntu | upstream | * |
| Tinyproxy | Ubuntu | xenial | * |
Developers often choose default values that leave the product as open and easy to use as possible out-of-the-box, under the assumption that the administrator can (or should) change the default value. However, this ease-of-use comes at a cost when the default is insecure and the administrator does not change it.