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
netrc(4)						     Kernel Interfaces Manual							  netrc(4)

NAME
netrc: .netrc - login information for ftp, rexec, and rexec() DESCRIPTION
The file contains login and initialization information used by the autologin process, by the library routine, and by the command (see ftp(1), rexec(3N), and remsh(1)), respectively. This file is optional. It exists, if at all, in the user's home directory. If the file contains password or account information for use other than for anonymous its owner must match the effective user ID of the current process. Its read, write, and execute mode bits for group and other must all be zero, and it must be readable by its owner. Oth- erwise, the file is ignored. The file can contain the following tokens, separated by whitespace (spaces, tabs, or newlines) or commas To include a comma as part of a token, enclose that token in quotation marks (). Identify a remote machine name. The autologin process searches the file for a token that matches the remote machine specified on the command line, as an command argument, or as the parameter of Once a match is made, the subsequent tokens are processed, stopping when the end-of-file is reached or another token or a token is encountered. If the remote machine name has an alias host name, and both the official host name and the alias are present in the file, the client gives precedence to the official host name over the alias when searching the file. If an alias is given as an entry to the command, and in the search from the top of the file to the bottom, the client finds the alias host name before it finds the official host name, it will use the alias's entry. However, if it finds the official host name first, it will use the official entry even though the alias host name also exists in the file. So the high precedence given to the official host name requires placing the official host name entry last in the file for when aliases exist. Same as except that matches any name. There can be only one token, and it must be after all tokens. This is normally used for as follows: This provides automatic anonymous login to machines not specified in This can be overridden in by using the flag to disable autologin. Identify a user on the remote machine. If this token is present, the or autologin process initiates a login using the specified name. If this token matches the user name used by the command option, or, by default, the local user name, uses the token, if present. Supply a password. If this token is present, the autologin process supplies the specified string, if the remote server requires a password as part of the login process. Note that if this token is present in the file for any user other than aborts the autologin process if the is readable by anyone other than the owner. Also note that the passwords in are not encrypted. Supply an additional account password for login. If this token is present, the autologin process supplies the specified string if the remote server requires an additional account password, or the autologin process initiates an command if it does not. Define an macro. This token is just like the command. A macro is defined with the specified name; its contents begin with the next line and continue until an empty line (consecutive newline characters) is encountered. If a macro named is defined, it is automatically executed as the last step in the autologin process. EXAMPLES
The following is a valid entry for the host whose account has the password WARNINGS
It is a security risk to have unencrypted passwords in a file. AUTHOR
was developed by the University of California, Berkeley. FILES
SEE ALSO
ftp(1), remsh(1), rexec(3N). netrc(4)