CVE-2022-41317
Published: 23 September 2022
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.
Priority
Status
| Package | Release | Status |
|---|---|---|
|
squid
Launchpad, Ubuntu, Debian |
bionic |
Does not exist
|
| focal |
Released
(4.10-1ubuntu1.7)
|
|
| jammy |
Released
(5.2-1ubuntu4.2)
|
|
| kinetic |
Released
(5.6-1ubuntu3)
|
|
| trusty |
Does not exist
|
|
| upstream |
Released
(5.7)
|
|
| xenial |
Does not exist
|
|
|
squid3
Launchpad, Ubuntu, Debian |
bionic |
Not vulnerable
|
| focal |
Does not exist
|
|
| jammy |
Does not exist
|
|
| trusty |
Not vulnerable
|
|
| upstream |
Not vulnerable
|
|
| xenial |
Not vulnerable
|
Severity score breakdown
| Parameter | Value |
|---|---|
| Base score | 6.5 |
| Attack vector | Network |
| Attack complexity | Low |
| Privileges required | Low |
| User interaction | None |
| Scope | Unchanged |
| Confidentiality | High |
| Integrity impact | None |
| Availability impact | None |
| Vector | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |