S-073: Vulnerability in SMBv2


 
Thread Tools Search this Thread
Special Forums Cybersecurity Security Advisories (RSS) S-073: Vulnerability in SMBv2
# 1  
Old 12-24-2007
S-073: Vulnerability in SMBv2

A remote code execution vulnerability exists in the SMBv2 protocol that could allow a remote anonymous attacker to run code with the privileges of the logged-on user. The risk is MEDIUM. Could allow a remote anonymous attacker to run code with the privileges of the logged-on user.


More...
Login or Register to Ask a Question

Previous Thread | Next Thread

5 More Discussions You Might Find Interesting

1. Red Hat

Use of SMBv2 in RHEL 6.3

I am mounting a shared drive from RHEL 6.3 system to Windows server 2008 R2 system and then copying files from RHEL system to Windows Server 2008 R2 system through a shell scripts.At present, Micro Soft declared SMBv1 as vulnerable.I am using "mount -t cifs" to mound the shared drive. Can I use... (2 Replies)
Discussion started by: Anjan Ganguly
2 Replies

2. IP Networking

Common Vulnerability

Hi there, I am trying to find info about the commonly used ports and how it can be vulnerable and to identify them? For example, I would like to identify how to man-in-the-middle using these ports 21(FTP),22(SSH),23(TELNET), (1 Reply)
Discussion started by: alvinoo
1 Replies

3. News, Links, Events and Announcements

Bash vulnerability

Not sure if there is a post about it here somewhere already. Anyway: Remote exploit vulnerability in bash CVE-2014-6271 | CSO Online (3 Replies)
Discussion started by: zaxxon
3 Replies

4. UNIX for Dummies Questions & Answers

Vulnerability Alerts

Aside from CERT, are there any additional sources for unix/linux vulnerabilities? (1 Reply)
Discussion started by: kmgrady01
1 Replies

5. Cybersecurity

SNMP Vulnerability

SNMP Vulnerability: In a few minutes wire services and other news sources will begin breaking a story about widespread vulnerabilities in SNMP (Simple Network Management Protocol). Exploits of the vulnerability cause systems to fail or to be taken over. The vulnerability can be found in... (1 Reply)
Discussion started by: dpatel
1 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)