|
Bugzilla – Full Text Bug Listing |
| Summary: | VUL-0: CVE-2005-1519: squid bugs | ||
|---|---|---|---|
| Product: | [Novell Products] SUSE Security Incidents | Reporter: | Ludwig Nussel <lnussel> |
| Component: | Incidents | Assignee: | Security Team bot <security-team> |
| Status: | RESOLVED FIXED | QA Contact: | Security Team bot <security-team> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | security-team |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | CVE-2005-1519: CVSS v2 Base Score: 6.4 (AV:N/AC:L/Au:N/C:N/I:P/A:P) | ||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Bug Depends on: | 90338 | ||
| Bug Blocks: | |||
| Attachments: |
all relevant lines from /var/log/squid/access.log
network traffic in libpcap format (just load into ethereal and "follow tcpstream") squid startup messages from /var/log/messages |
||
|
Description
Ludwig Nussel
2005-05-12 14:54:38 UTC
Thanks. :-) I also think that these problems are of minor severity. I'm currently still working on the unace issue (as expected: takes a bit longer to dig in). So, if there is no real need to build an update (e.g. from L3), then we should wait till next major problem and include it then. As argued before: LATER. SM-Tracker-1628 update in the queue Either this fix or the fix to Bug #90338 breaks squid on sles9-s390x (and only that!). Looks like squid runs into some weired DNS resolver problems. The setup I used: - use s390zvc24 as proxy for all protocols supported by firefox - access http://www.novell.com/linux/ After waiting for some seconds you get: --------------------------------- The requested URL could not be retrieved While trying to retrieve the URL: http://www.novell.com/linux/ The following error was encountered: Unable to determine IP address from host name for www.novell.com The dnsserver returned: Timeout This means that: The cache was not able to resolve the hostname presented in the URL. Check if the address is correct. Your cache administrator is webmaster. Generated Wed, 29 Jun 2005 09:22:00 GMT by s390zvc24.suse.de (squid/2.5.STABLE5) ------------------------------- I tried both the GA version of squid for sles9-s390x and the last maintenance update (patch 10032 - md5sum fce96418deb2ca446635af24ff7e4a01). These work! Logs/attachments follow. Created attachment 40344 [details]
all relevant lines from /var/log/squid/access.log
Created attachment 40346 [details]
network traffic in libpcap format (just load into ethereal and "follow tcpstream")
Created attachment 40347 [details]
squid startup messages from /var/log/messages
reassign to maintainer found the problem (a wrong pointer declaration in upstream patch, might break on _any_ 64bit architecture) and fixed it. submitted new packages. reassigning back to security-team for further processing. note: this affects only: 9.1 (SLES9), 9.2 and 9.3 there is another (upstream) patch for the older squid versions, where this declaration is correct. therefore SLES8, 8.2, 9.0 are not affected. I realized that this problem is already fixed (different) upstream and a change of 9.3 is not necessary. So, it re-work was only necessary for: 9.1 (SLES9) and 9.2. I removed 9.3 submission. packages approved the dns query issue is CAN-2005-1519 CVE-2005-1519: CVSS v2 Base Score: 6.4 (AV:N/AC:L/Au:N/C:N/I:P/A:P) |