CVE-1999-0223: Low severity Sun SunOS vulnerability
Solaris syslogd crashes when receiving a message from a host that doesn't have an inverse DNS entry.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
Ensure hosts that send syslog messages to the Solaris syslogd have inverse DNS (PTR) entries by adding appropriate PTR records in DNS so that syslogd will not receive messages from hosts without reverse DNS.
DNS (PTR records) PTR record presence = present - Compensating control
Restrict which hosts can send syslog messages to the Solaris system (for example via firewall rules, ACLs, or on-network filtering). Block or drop syslog/UDP-514 (or configured syslog port) traffic from untrusted IPs or from hosts that do not have valid reverse DNS entries until a vendor fix is available.
Event History
Frequently Asked Questions
What is the severity of CVE-1999-0223?
CVE-1999-0223 is considered to have a moderate severity as it can cause system outages.
How do I fix CVE-1999-0223?
To fix CVE-1999-0223, ensure that your system is configured to validate incoming messages from hosts.
What systems are affected by CVE-1999-0223?
CVE-1999-0223 affects Solaris systems running SunOS version 5.4.
What are the potential consequences of CVE-1999-0223?
The potential consequences of CVE-1999-0223 include syslogd crashes leading to loss of logging functionality.
Is there a patch available for CVE-1999-0223?
Yes, a patch is available that addresses the issue caused by CVE-1999-0223, specific to SunOS 5.4.