Vulnerabilities > CVE-2008-4037 - Improper Authentication vulnerability in Microsoft products
Microsoft Windows 2000 Gold through SP4, XP Gold through SP3, Server 2003 SP1 and SP2, Vista Gold and SP1, and Server 2008 allows remote SMB servers to execute arbitrary code on a client machine by replaying the NTLM credentials of a client user, as demonstrated by backrush, aka "SMB Credential Reflection Vulnerability." NOTE: some reliable sources report that this vulnerability exists because of an insufficient fix for CVE-2000-0834.
Common Weakness Enumeration (CWE)
Common Attack Pattern Enumeration and Classification (CAPEC)
- Authentication Abuse An attacker obtains unauthorized access to an application, service or device either through knowledge of the inherent weaknesses of an authentication mechanism, or by exploiting a flaw in the authentication scheme's implementation. In such an attack an authentication mechanism is functioning but a carefully controlled sequence of events causes the mechanism to grant access to the attacker. This attack may exploit assumptions made by the target's authentication procedures, such as assumptions regarding trust relationships or assumptions regarding the generation of secret values. This attack differs from Authentication Bypass attacks in that Authentication Abuse allows the attacker to be certified as a valid user through illegitimate means, while Authentication Bypass allows the user to access protected material without ever being certified as an authenticated user. This attack does not rely on prior sessions established by successfully authenticating users, as relied upon for the "Exploitation of Session Variables, Resource IDs and other Trusted Credentials" attack patterns.
- Exploiting Trust in Client (aka Make the Client Invisible) An attack of this type exploits a programs' vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client. An attacker executes this type of attack by placing themselves in the communication channel between client and server such that communication directly to the server is possible where the server believes it is communicating only with a valid client. There are numerous variations of this type of attack.
- Utilizing REST's Trust in the System Resource to Register Man in the Middle This attack utilizes a REST(REpresentational State Transfer)-style applications' trust in the system resources and environment to place man in the middle once SSL is terminated. Rest applications premise is that they leverage existing infrastructure to deliver web services functionality. An example of this is a Rest application that uses HTTP Get methods and receives a HTTP response with an XML document. These Rest style web services are deployed on existing infrastructure such as Apache and IIS web servers with no SOAP stack required. Unfortunately from a security standpoint, there frequently is no interoperable identity security mechanism deployed, so Rest developers often fall back to SSL to deliver security. In large data centers, SSL is typically terminated at the edge of the network - at the firewall, load balancer, or router. Once the SSL is terminated the HTTP request is in the clear (unless developers have hashed or encrypted the values, but this is rare). The attacker can utilize a sniffer such as Wireshark to snapshot the credentials, such as username and password that are passed in the clear once SSL is terminated. Once the attacker gathers these credentials, they can submit requests to the web service provider just as authorized user do. There is not typically an authentication on the client side, beyond what is passed in the request itself so once this is compromised, then this is generally sufficient to compromise the service's authentication scheme.
- Man in the Middle Attack This type of attack targets the communication between two components (typically client and server). The attacker places himself in the communication channel between the two components. Whenever one component attempts to communicate with the other (data flow, authentication challenges, etc.), the data first goes to the attacker, who has the opportunity to observe or alter it, and it is then passed on to the other component as if it was never intercepted. This interposition is transparent leaving the two compromised components unaware of the potential corruption or leakage of their communications. The potential for Man-in-the-Middle attacks yields an implicit lack of trust in communication or identify between two components.
description Microsoft Windows SMB Relay Code Execution. CVE-2008-4037. Remote exploit for windows platform id EDB-ID:16360 last seen 2016-02-01 modified 2010-09-21 published 2010-09-21 reporter metasploit source https://www.exploit-db.com/download/16360/ title Microsoft Windows SMB Relay Code Execution description SmbRelay3 NTLM Replay Attack Tool/Exploit (MS08-068). CVE-2008-4037. Remote exploit for windows platform file exploits/windows/remote/7125.txt id EDB-ID:7125 last seen 2016-02-01 modified 2008-11-14 platform windows port published 2008-11-14 reporter Andres Tarasco source https://www.exploit-db.com/download/7125/ title SmbRelay3 NTLM Replay Attack Tool/Exploit MS08-068 type remote description MS Windows SMB Authentication Remote Exploit. CVE-2008-4037. Remote exploit for windows platform id EDB-ID:20 last seen 2016-01-31 modified 2003-04-25 published 2003-04-25 reporter Haamed Gheibi source https://www.exploit-db.com/download/20/ title Microsoft Windows SMB - Authentication Remote Exploit
|description||This module will relay SMB authentication requests to another host, gaining access to an authenticated SMB session if successful. If the connecting user is an administrator and network logins are allowed to the target machine, this module will execute an arbitrary payload. To exploit this, the target system must try to authenticate to this module. The easiest way to force a SMB authentication attempt is by embedding a UNC path (\\\SERVER\SHARE) into a web page or email message. When the victim views the web page or email, their system will automatically connect to the server specified in the UNC share (the IP address of the system running this module) and attempt to authenticate. Unfortunately, this module is not able to clean up after itself. The service and payload file listed in the output will need to be manually removed after access has been gained. The service created by this tool uses a randomly chosen name and description, so the services list can become cluttered after repeated exploitation. The SMB authentication relay attack was first reported by Sir Dystic on March 31st, 2001 at @lanta.con in Atlanta, Georgia. On November 11th 2008 Microsoft released bulletin MS08-068. This bulletin includes a patch which prevents the relaying of challenge keys back to the host which issued them, preventing this exploit from working in the default configuration. It is still possible to set the SMBHOST parameter to a third-party host that the victim is authorized to access, but the "reflection" attack has been effectively broken.|
|title||MS08-068 Microsoft Windows SMB Relay Code Execution|
|impact||Remote Code Execution|
|title||Vulnerability in SMB Could Allow Remote Code|
|NASL family||Windows : Microsoft Bulletins|
|description||The remote version of Windows contains a version of SMB (Server Message Block) protocol that is vulnerable to a credentials reflection attack. An attacker may exploit this flaw to elevate his privileges and gain control of the remote host.|
|reporter||This script is Copyright (C) 2008-2018 Tenable Network Security, Inc.|
|title||MS08-068: Vulnerability in SMB Could Allow Remote Code Execution (957097)|
|description||Microsoft Windows 2000 Gold through SP4, XP Gold through SP3, Server 2003 SP1 and SP2, Vista Gold and SP1, and Server 2008 allows remote SMB servers to execute arbitrary code on a client machine by replaying the NTLM credentials of a client user, as demonstrated by backrush, aka "SMB Credential Reflection Vulnerability." NOTE: some reliable sources report that this vulnerability exists because of an insufficient fix for CVE-2000-0834.|
|title||SMB Credential Reflection Vulnerability|
|reporter||H D Moore|
|title||Microsoft Windows SMB Relay Code Execution|
|description||Windows SMB credential reflection vulnerability|
|description||BUGTRAQ ID: 7385 CVE(CAN) ID: CVE-2008-4037 Windows是微软发布的非常流行的操作系统。 当用户连接到攻击者的SMB服务器时，Microsoft服务器消息块（SMB）协议处理NTLM凭据的方式存在远程代码执行漏洞，允许攻击者重放用户凭据，并在登录用户的下文中执行代码。如果用户使用管理用户权限登录，成功利用此漏洞的攻击者便可完全控制受影响的系统。攻击者可随后安装程序；查看、更改或删除数据，或者创建拥有完全用户权限的新帐户。那些帐户被配置为拥有较少系统用户权限的用户比具有管理用户权限的用户受到的影响要小。 Microsoft Windows XP SP3 Microsoft Windows XP SP2 Microsoft Windows Vista SP1 Microsoft Windows Vista Microsoft Windows Server 2008 Microsoft Windows Server 2003 SP2 Microsoft Windows Server 2003 SP1 Microsoft Windows 2000SP4 临时解决方法： * 在防火墙处阻止TCP 139和445端口。 厂商补丁： Microsoft --------- Microsoft已经为此发布了一个安全公告（MS08-068）以及相应补丁: MS08-068：Vulnerability in SMB Could Allow Remote Code Execution (957097) 链接：<a href=http://www.microsoft.com/technet/security/bulletin/ms08-068.mspx?pf=true target=_blank>http://www.microsoft.com/technet/security/bulletin/ms08-068.mspx?pf=true</a>|
|title||Microsoft Windows SMB凭据反射漏洞（MS08-068）|