squid: Improper access restriction in url_regex may lead to security bypass
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
Configuration 3 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Enterprise Linux 8 | |||
| squid:4-8030020200828070549.30b713e6 | cpe:/a:redhat:enterprise_linux:8 | RHSA-2020:4743 | 2020-11-04T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-2278-1 | squid3 security update |
Debian DSA |
DSA-4682-1 | squid security update |
EUVD |
EUVD-2019-4119 | An issue was discovered in Squid through 4.7. When handling requests from users, Squid checks its rules to see if the request should be denied. Squid by default comes with rules to block access to the Cache Manager, which serves detailed server information meant for the maintainer. This rule is implemented via url_regex. The handler for url_regex rules URL decodes an incoming request. This allows an attacker to encode their URL to bypass the url_regex check, and gain access to the blocked resource. |
Ubuntu USN |
USN-4446-1 | Squid vulnerabilities |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 3.9% (3.862% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.