| Summary: | net-misc/dhcpcd-3.1.7 logging DoS | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Gentoo Security | Reporter: | Duncan <1i5t5.duncan> | ||||
| Component: | Vulnerabilities | Assignee: | Gentoo's Team for Core System packages <base-system> | ||||
| Status: | RESOLVED FIXED | ||||||
| Severity: | normal | CC: | lkundrak, roy, uberlord | ||||
| Priority: | High | ||||||
| Version: | unspecified | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Package list: | Runtime testing required: | --- | |||||
| Attachments: |
|
||||||
|
Description
Duncan
2007-11-06 10:22:24 UTC
Thanks for your report. In my opinion this is not a security issue. Extensive logging is not anything that would be considered a DoS, as a logging can be triggered remotely arbitrairily -- via http request, ftp transfer, logging in and out, etc. The fact that the daemon no longer server its purpose has no security implications as it can not be triggered by anyone (dhcpcd is not setuid, right?), just by an authenticated user with privileges to send the daemon process a signal (superuser). Furthermore he notices what has happened as the lease does not get renewed and problem is logged. Created attachment 135354 [details, diff]
clear signals when read
This patch should fix this. I also disagree with it being a security issue.
agreed, we do not consider client DoS as a security issue. Reassigning to maintainer (base-system). dhcpcd-3.1.8 - hopefully in the tree now - aleviates this a little. It should only report the address being added each time. |