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
RUSERS(1)						    BSD General Commands Manual 						 RUSERS(1)

NAME
rusers -- who is logged in to machines on local network SYNOPSIS
rusers [-al] [host ...] DESCRIPTION
The rusers command produces output similar to who(1), but for the list of hosts or all machines on the local network. For each host respond- ing to the rusers query, the hostname with the names of the users currently logged on is printed on each line. The rusers command will wait for one minute to catch late responders. The following options are available: -a Print all machines responding even if no one is currently logged in. -l Print a long format listing. This includes the user name, host name, tty that the user is logged in to, the date and time the user logged in, the amount of time since the user typed on the keyboard, and the remote host they logged in from (if applicable). DIAGNOSTICS
rusers: RPC: Program not registered The rpc.rusersd(8) daemon has not been started on the remote host. rusers: RPC: Timed out A communication error occurred. Either the network is excessively congested, or the rpc.rusersd(8) daemon has termi- nated on the remote host. rusers: RPC: Port mapper failure - RPC: Timed out The remote host is not running the portmapper (see rpcbind(8)), and cannot accommodate any RPC-based services. The host may be down. SEE ALSO
rwho(1), users(1), who(1), rpc.rusersd(8), rpcbind(8) HISTORY
The rusers command appeared in Sun-OS. BUGS
The sorting options are not implemented. BSD
April 23, 1991 BSD