| Summary: | squid new security issues SQUID-2018:1 (CVE-2018-1000024) and SQUID-2018:2 (CVE-2018-1000027) | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | David Walser <luigiwalser> |
| Component: | Security | Assignee: | QA Team <qa-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | Sec team <security> |
| Severity: | normal | ||
| Priority: | Normal | CC: | herman.viaene, sysadmin-bugs, tarazed25 |
| Version: | 6 | Keywords: | advisory, has_procedure, validated_update |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | MGA5TOO MGA5-64-OK MGA6-64-OK MGA5-32-OK | ||
| Source RPM: | squid-3.5.26-1.mga6.src.rpm | CVE: | |
| Status comment: | |||
|
Description
David Walser
2018-01-22 14:18:48 CET
Testing hints: https://bugs.mageia.org/show_bug.cgi?id=14004#c3 https://bugs.mageia.org/show_bug.cgi?id=16304#c14 Keywords:
(none) =>
has_procedure Posting this through an updated Squid on Mageia 5 x86_64. Whiteboard:
MGA5TOO =>
MGA5TOO MGA5-64-OK MGA5-32 on Dell Latitude D600 Xfce No installation issues I must be missing something Installed squid checked httpd is running started squid imported squid.conf from bug 16304 restarte5 squid Changed proxy settings in Firefox Surfing to https://www.magei.org gives me "The proxyserver refuses connection". CC:
(none) =>
herman.viaene Don't use a squid.conf from an older Squid version. The one shipped with the package should work just fine. I had the same problem with the default squid.conf, that's why I started hunting for more info. Did you start the service? You didn't give enough information for us to know what you did or to help diagnose it. I have been trying this for Mageia 6 x86_64 and have hit similar problems. The 'refusing connection' message comes up only when squid is stopped. When it is enabled all sites time out. The only difference between the default config and the downloaded one is the line: http_access deny to_localhost which is commented out in the default. Switching back to the default makes no difference. After configuring the proxy settings in firefox restarted squid. Shorewall has ports 3128/tcp and 3128/udp enabled Oops - forgot to restart apache! Done that and restarted squid. firefox settings are: manual configuration -> localhost|127.0.0.1 -> port 3128 All internet connections time out. CC:
(none) =>
tarazed25 It should say refusing connections when Squid is stopped. It works when it's running, right? Yes, correct. A slight advance, maybe. Went back into firefox and tried to wipe all the other settings, leaving just the manual ones. Switched from SOCKS v5 to SOCKS 4 (no idea what that means) but the SOCKS entry is blank. After that restarting squid allowed access to the internet. Cool, it's working then. The SOCKS entry should indeed be blank. Thanks David. So that is all that is needed? And, @Herman. Anything there which helps you? Yes, if it works, it should be fine.
Len Lawrence
2018-01-24 00:54:05 CET
Whiteboard:
MGA5TOO MGA5-64-OK =>
MGA5TOO MGA5-64-OK MGA6-64-OK Booted this morning. Squid and httpd running, gives "The proxyserver refuses connection" (or whatever it might be in english, I am running dutch) Stopped squid, reinstated its original squid.conf, started squid again, still same message. Cleared the socks entry as Comment 11, refreshed the https page and now it comes thru. Then browsed to http://localhost/cgi-bin/cachemgr.cgi, all looks OK Whiteboard:
MGA5TOO MGA5-64-OK MGA6-64-OK =>
MGA5TOO MGA5-64-OK MGA6-64-OK MGA5-32-OK
Lewis Smith
2018-01-24 21:22:07 CET
Keywords:
(none) =>
advisory, validated_update An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGASA-2018-0095.html Resolution:
(none) =>
FIXED CVE-2018-1000024 and CVE-2018-1000027 have been assigned: http://openwall.com/lists/oss-security/2018/01/29/1 http://openwall.com/lists/oss-security/2018/01/29/2 Summary:
squid new security issues SQUID-2018:1 and SQUID-2018:2 =>
squid new security issues SQUID-2018:1 (CVE-2018-1000024) and SQUID-2018:2 (CVE-2018-1000027) |