RE: Access to well-known ports on Win2K
From: Rangan, Govindaraj (govindr@ti.com)Date: 10/31/02
- Previous message: Corey Snow: "RE: WINNT security priviledge escalation attack"
- Next in thread: Raghu Chinthoju: "RE: Access to well-known ports on Win2K"
- Reply: Raghu Chinthoju: "RE: Access to well-known ports on Win2K"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Rangan, Govindaraj" <govindr@ti.com> To: "'focus-ms@securityfocus.com'" <focus-ms@securityfocus.com> Date: Thu, 31 Oct 2002 10:29:16 +0530
Hi All,
Greetings.
Do all users on Win2K have access to the well-known ports? This
question arose when I was doing some security tests in a heterogeneous
environment with Windows and Solaris boxes. Solaris RSHD's only security is
that before allowing access, it checks the source host and source tcp port.
The host should be in hosts.equiv or .rhosts and the source tcp port should
be one of well known ports (0-1023). The rsh client is a setuid script and
starts as root. However on Windows 2000, it is possible for any user (not
necessarily an admin user) to open a "well known port" to connect to any
rshd.
Can we restrict access to well known ports to a certain user or
group? If not, the secure way is that Solaris hosts shouldn't trust Windows
hosts. Your help in resolving this is highly appreciated.
Regards,
Govind
- Previous message: Corey Snow: "RE: WINNT security priviledge escalation attack"
- Next in thread: Raghu Chinthoju: "RE: Access to well-known ports on Win2K"
- Reply: Raghu Chinthoju: "RE: Access to well-known ports on Win2K"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
