Bug 141547
Summary: | When application Nessus is running. cupsd starts to take more and more CPU, until hangs the application. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Mikhail Utin <mutin> |
Component: | cups | Assignee: | Tim Waugh <twaugh> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | CC: | rainer.kraft |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i586 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | FC4 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-09-09 13:57:58 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Mikhail Utin
2004-12-01 22:38:30 UTC
This is quite vague -- can you be more specific please? Does printing still work after you use Nessus? I have the same problem. Printing stops also. I cannot even kill cupsd with kill -15, I have to kill it hard with kill -9. All my CUPS instances show this behaviour. This is a serious security issue. It's very easy to take a CUPS print daemon down by overloading the WebGui with a scanner like Nessus. Please provide specific details so that I can analyze this problem properly. Does this only work from localhost? What messages are written to error_log? What does 'gdb' say the stack trace is at that point? etc etc etc. I've upgraded CUPS to 1.1.23 and now it's much more stable and it survives the Nessus scans. If not, I will update you with the needed information. But basically: It scanned over the network, so it's not localhost. There are no messages written to error_log and I've not used gdb for a stack trace. |