Bugtraq mailing list archives
syslog/udp
From: newsham () uhunix uhcc hawaii edu (Tim Newsham )
Date: Sun, 20 Feb 94 12:12:10 HST
Hi, If you are running syslogd on your machine and you dont receive remote logging to that machine you should probably consider removing the remote function of the program. Besides being another possible security risk a person may easily corrupt your audit logs though this port. It is quite easy to send fake messages to the syslogd at any facility and level. An easy way to fix this would probably be to change the line: int nfds, readfds = FDMASK(funix) | inetm | klogm; to int nfds, readfds = FDMASK(funix) | klogm; This will keep the inet socket from ever getting selected and read. I have not tested this however. An access control list would do no good here since the packets are UDP and source address is quite easy to forge. Tim N.
Current thread:
- syslog/udp Tim Newsham (Feb 20)
- <Possible follow-ups>
- Re: syslog/udp Dave Hayes (Feb 22)
- Re: syslog/udp John Hawkinson (Feb 23)
- Security problem in C news and INN Featherlace (Feb 23)
- Re: Security problem in C news and INN Casper Dik (Feb 24)
- Re: Security problem in C news and INN Perry E. Metzger (Feb 24)
- Re: syslog/udp John Hawkinson (Feb 23)
- Re: syslog/udp scott () santafe edu (Feb 23)
- Re: syslog/udp Tim Newsham (Feb 23)
- Re: syslog/udp Julian Assange (Feb 23)
- daemon() Jim Wright (Feb 24)
- Thanks! Dave Hayes (Feb 23)