S-320: Citect CitectSCADA Vulnerability


 
Thread Tools Search this Thread
Special Forums Cybersecurity Security Advisories (RSS) S-320: Citect CitectSCADA Vulnerability
# 1  
Old 06-19-2008
S-320: Citect CitectSCADA Vulnerability

Citect CitectSCADA contains a remotely accessible buffer overflow vulnerability which may allow a remote attacker to execute arbitrary code. The risk is MEDIUM. A remote, unauthenticated attacker may be able to execute arbitrary code or cause a denial of service.


More...
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

How to install Linux on an external 320 gigabyte hard drive

Hi all, I would to know if I can install Linux on an external 320 gigabyte hard drive..I have Windows XP on my internal hard drive which is 80 GB , but this installation on 320 external HDD is for testing purpose If it is possible to install Linux on the external drive, will it cause any... (5 Replies)
Discussion started by: bsandeep_80
5 Replies

2. SCO

ultra 320 scsi raid controller driver for sco 5.0.6

I am facing a problem to install sco 5.0.6 in Dell Power Edge SC1420 which raid controller is ultra 320 scsi raid controller . how/from where to download the ultra 320 scsi raid controller driver for sco 5.0.6. Plz help with any idea karzon (1 Reply)
Discussion started by: karzon
1 Replies

3. SCO

configure Adaptec 29320ALP Ultra 320 SCSI Card in IBM X3400

I am installing SCO UNIX 5.0.6 in X3400, every thing are install except Adaptec 29320ALP Card (Attached DAT Drive) because their driver are available in btld formate Fllopy DISk and SCO Unix 5.0.6 not support USB Floppy, Can anybody inform us any other method to installed the Adaptec Ultra 120... (3 Replies)
Discussion started by: hafizurr
3 Replies
Login or Register to Ask a Question
USERFILE(5)							File Formats Manual						       USERFILE(5)

Name
       USERFILE - defines uucp security

Syntax
       /usr/lib/uucp/USERFILE

Description
       The  utility  uses the USERFILE to establish what access a remote system can have to the local system.  An entry should exist for each sys-
       tem.  If no entries exist for a particular system, the default entries are used.  The entries for particular  systems  have  the  following
       format:

       login-name , node-name X # path-name

       login-name
		 The name with which the remote system logs in.

       node-name The name of the remote node.

       X#	 The  execution  level	for  the remote system.  The remote system can execute commands defined in the file that have an execution
		 level less than or equal to the number #.

       path-name The remote system can access anything at the local system with this prefix.

       Two entries must also be provided for systems not otherwise listed:

	    remote, X# path-name ...
	    local, X# path-name ...

       These entries define the execution level and access pathnames for the local system and all remote systems not defined by specific entries.

Examples
       remote, X1 /usr/spool/uucppublic
       local, X9 /
       max,systemY /usr/sources /usr/src/share
       max,systemZ X3 /usr
       In the above example, the node named systemY with the login name max has access to anything with the pathname prefixes and The  node  named
       systemZ	with  the  login  name max can execute commands defined in with an execution level of 3 or lower.  It can access anything with the
       pathname prefix

       Any other remote systems can execute commands defined in with an execution level of 1 or 0.  They can access  anything  with  the  pathname
       prefix of

       Users on the local system can execute any of the commands defined in and access anything on the system.

See Also
       Guide to the uucp Utility

																       USERFILE(5)