Vulnerabilities > CVE-2009-0695 - Improper Authentication vulnerability in Dell Wyse Device Manager 4.7.0/4.7.1/4.7.2
Attack vector
NETWORK Attack complexity
LOW Privileges required
NONE Confidentiality impact
PARTIAL Integrity impact
PARTIAL Availability impact
PARTIAL Summary
hagent.exe in Wyse Device Manager (WDM) 4.7.x does not require authentication for commands, which allows remote attackers to obtain management access via a crafted query, as demonstrated by a V52 query that triggers a power-off action.
Vulnerable Configurations
Part | Description | Count |
---|---|---|
Application | 3 |
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.
Exploit-Db
description Wyse Rapport Hagent Fake Hserver Command Execution. CVE-2009-0695. Remote exploits for multiple platform id EDB-ID:9934 last seen 2016-02-01 modified 2009-07-10 published 2009-07-10 reporter kf source https://www.exploit-db.com/download/9934/ title Wyse Rapport Hagent Fake Hserver - Command Execution description Wyse Rapport Hagent Fake Hserver Command Execution. CVE-2009-0695. Remote exploits for multiple platform id EDB-ID:16287 last seen 2016-02-01 modified 2010-11-11 published 2010-11-11 reporter metasploit source https://www.exploit-db.com/download/16287/ title Wyse Rapport Hagent Fake Hserver Command Execution description Wyse - Machine Remote Power off (DOS) without any privilege. CVE-2009-0693,CVE-2009-0695. Dos exploit for hardware platform file exploits/hardware/dos/19137.rb id EDB-ID:19137 last seen 2016-02-02 modified 2012-06-14 platform hardware port published 2012-06-14 reporter it.solunium source https://www.exploit-db.com/download/19137/ title Wyse - Machine Remote Power off DOS without any privilege type dos
Metasploit
description | This module exploits the Wyse Rapport Hagent service by pretending to be a legitimate server. This process involves starting both HTTP and FTP services on the attacker side, then contacting the Hagent service of the target and indicating that an update is available. The target will then download the payload wrapped in an executable from the FTP service. |
id | MSF:EXPLOIT/MULTI/WYSE/HAGENT_UNTRUSTED_HSDATA |
last seen | 2020-04-11 |
modified | 2017-07-24 |
published | 2009-08-19 |
references | |
reporter | Rapid7 |
source | https://github.com/rapid7/metasploit-framework/blob/master//modules/exploits/multi/wyse/hagent_untrusted_hsdata.rb |
title | Wyse Rapport Hagent Fake Hserver Command Execution |
Nessus
NASL family | Windows |
NASL id | WYSE_WDM_BUFFER_OVERFLOW.NASL |
description | Wyse Device Manager is installed on the remote system. The installed version is affected by a buffer overflow vulnerability. By sending a specially crafted request to the server, it may be possible for an unauthorized attacker to crash the server or execute arbitrary commands on the remote system with system level privileges. |
last seen | 2020-06-01 |
modified | 2020-06-02 |
plugin id | 40333 |
published | 2009-07-21 |
reporter | This script is Copyright (C) 2009-2018 Tenable Network Security, Inc. |
source | https://www.tenable.com/plugins/nessus/40333 |
title | Wyse Device Manager Buffer Overflow |
code |
|
Packetstorm
data source https://packetstormsecurity.com/files/download/82289/hagent_untrusted_hsdata.rb.txt id PACKETSTORM:82289 last seen 2016-12-05 published 2009-10-28 reporter Kevin Finisterre source https://packetstormsecurity.com/files/82289/Wyse-Rapport-Hagent-Fake-Hserver-Command-Execution.html title Wyse Rapport Hagent Fake Hserver Command Execution data source https://packetstormsecurity.com/files/download/113683/wyseoff-dos.rb.txt id PACKETSTORM:113683 last seen 2016-12-05 published 2012-06-14 reporter it.solunium source https://packetstormsecurity.com/files/113683/Wyse-Machine-Remote-Power-Off-Denial-Of-Service.html title Wyse Machine Remote Power Off Denial Of Service