First published: Sun Jun 04 2000(Updated: )
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.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Xinetd Xinetd | =2.1.88_pre2 | |
Xinetd Xinetd | =2.1.88_pre1 | |
Xinetd Xinetd | =2.1.89_pre3 | |
Xinetd Xinetd | =2.1.89_pre4 | |
Xinetd Xinetd | =2.1.89_pre2 | |
Xinetd Xinetd | =2.1.89_pre1 | |
Xinetd Xinetd | =2.1.89_pre5 | |
Xinetd Xinetd | =2.1.87 | |
Xinetd Xinetd | =2.1.88 | |
=2.1.87 | ||
=2.1.88 | ||
=2.1.88_pre1 | ||
=2.1.88_pre2 | ||
=2.1.89_pre1 | ||
=2.1.89_pre2 | ||
=2.1.89_pre3 | ||
=2.1.89_pre4 | ||
=2.1.89_pre5 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.