An issue was discovered in Squid 4.9 through 4.17 and 5.0.6 through 5.6. Due to inconsistent handling of internal URIs, there can be Exposure of Sensitive Information about clients using the proxy via an HTTPS request to an internal cache manager URL. This is fixed in 5.7.
The product compares two entities in a security-relevant context, but the comparison is incorrect, which may lead to resultant weaknesses.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Squid | Squid-cache | 4.9 (including) | 4.17 (including) |
| Squid | Squid-cache | 5.0.6 (including) | 5.7 (excluding) |
| Squid | Ubuntu | devel | * |
| Squid | Ubuntu | focal | * |
| Squid | Ubuntu | jammy | * |
| Squid | Ubuntu | kinetic | * |
| Squid | Ubuntu | upstream | * |
This Pillar covers several possibilities: