RE: Authentication Vulnerability in NetScreen ScreenOS

From: Hugo van der Kooij (hvdkooij_at_vanderkooij.org)
Date: 06/26/03

  • Next message: Joel Eriksson: "Bahamut IRCd <= 1.4.35 and several derived daemons" 
    Date: Thu, 26 Jun 2003 21:33:13 +0200 (CEST)
To: bugtraq@securityfocus.com

    On Thu, 26 Jun 2003, Brian Soby wrote:

    > >However, after a user is authenticated, anyone else may also access the
    > >protected services if they orginate from the same source IP address (NAT'd
    > >network). The authentication mechanism is designed to authenticate based on
    > >source-ip address only.
    >
    > Most firewalls track authenticated users based on the client's source IP
    > address. If you need a stronger method, you could always use the Netscreen
    > Remote client software and require a secure tunnel from the clients to get
    > to your protected resources.

    The Check Point firewall has the option to do client authentication which
    is a lot of fun if you happen to hide a full class B network behind a
    single address.

    It is not a security breach in the sense that the software is doing
    something inappropriate. The security breach is in the mind of the person
    thinking that IP addresses can be trusted for security purposes.

    Hugo. 

    -- 
 All email sent to me is bound to the rules described on my homepage.
    hvdkooij@vanderkooij.org		http://hvdkooij.xs4all.nl/
	    Don't meddle in the affairs of sysadmins,
	    for they are subtle and quick to anger.
  • Next message: Joel Eriksson: "Bahamut IRCd <= 1.4.35 and several derived daemons"

    Relevant Pages

    • Re: SecuRemote Client and Netfilter NAT
      ... I am not sure about this as I am unfamiliar with the aforementioned client, ... > box is NAT'ing the internal network using iptables 1.2.6a. ... > a packet analysis revealed that UDP 259 was needed for authentication. ...
      (Security-Basics)
    • Re: 2003 AD XP Client domain name change
      ... One of the main problems with this scenario is that once a 2K/XP client ... Currently have an AD 2003 test network setup in interim ... authentication purposes. ... connection with the server ...
      (microsoft.public.win2000.active_directory)
    • RE: Wireless Security Notes and Findings (from this list and other places)
      ... There are two general areas of wireless security: Authentication and ... authentication standard that works with wireless networks. ... client computer runs a client program to connect to the network with a ...
      (Security-Basics)
    • Re: IP address assignment problem
      ... I have a little problem and seek for ur thoughts, let's assume I'm in a very open environment where everyone can very easily try to get his/her laptop on the network and IP addresses are assigned by a DHCP server and we are in a domain environment, how do I prevent machines that are not part of our domain to be assigned an IP address? ... This approach doesn't stop your rogue clients from connecting to other clients, but merely doesn't give them the information they normally need to do so. ... Using 802.1x, your workstations authenticate through the switch to a radius server before they are allowed any connectivity. ... This authentication can use X.509 certificates, computer account credentials from AD, or whatever else you'd normally configure radius to authenticate with. ...
      (Focus-Microsoft)
    • Re: Kerberos machine authentication - apparent authentication failures
      ... When you joined your computer to the domain your wireless network card was ... denied access until you can authenticate to a domain controller as a user. ... While kerberos is the default authentication protocol of choice, ...
      (microsoft.public.windows.server.security)