CVE-2000-0536: High severity xinetd xinetd vulnerability
xinetd 2.1.8.x does not properly restrict connections if hostnames are used for access control and the connecting host does not have a reverse DNS entry.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
Do not rely on hostnames for xinetd access control. Reconfigure xinetd service access entries to use IP addresses or network ranges instead of hostnames.
SUSE xinetd use hostnames for access control = disabled - Compensating control
Restrict access to the affected services at the network perimeter (firewall/ACL) to trusted IP addresses or networks to mitigate the incorrect hostname-based access control behavior.
- Operational
Ensure connecting hosts have reverse DNS (PTR) records so hostname-based access control can correctly identify clients.
Event History
Frequently Asked Questions
What is the severity of CVE-2000-0536?
CVE-2000-0536 is classified as a moderate severity vulnerability due to potential unauthorized access.
How do I fix CVE-2000-0536?
To fix CVE-2000-0536, you should update xinetd to a patched version that addresses the reverse DNS validation issue.
What versions of xinetd are affected by CVE-2000-0536?
CVE-2000-0536 affects xinetd versions 2.1.87 through 2.1.89_pre5.
What does CVE-2000-0536 vulnerability exploit?
CVE-2000-0536 exploits weaknesses in hostname-based access controls when reverse DNS entries are not present.
Is CVE-2000-0536 a local or remote vulnerability?
CVE-2000-0536 is considered a remote vulnerability, as it allows remote attackers to gain unauthorized access.