Showing papers on "File inclusion vulnerability published in 2005"

Method, system and apparatus for assessing vulnerability in web services

Abstract: Disclosed is a computer implemented method for testing a Web service to determine whether the Web service is vulnerable to at least one known vulnerability. A test case is created and executed for the Web service to determine whether the Web service is vulnerable to the vulnerability. The test case is based on at least one vulnerability definition, at least one Web service operation or port, and at least one control request. The vulnerability definition includes information required to create a request and an expected result. Also disclosed is a computer implemented method of testing a Web service to determine whether the Web service complies with a policy, for example a security or vulnerability policy. A test case is created and executed for the Web service to determine if the Web service complies to the policy.

SSLv2 Malformed Client Key Remote Buffer Overflow Vuln

Abstract: This chapter discusses a case study involving a secure socket layer version 2 (SSLv2) Malformed Client Key Remote Buffer Overflow Vulnerability. Some vulnerability is present in the OpenSSL software library in the SSLv2key exchange portion. The vulnerability is commonly referred to as the OpenSSL SSLv2 Malformed Client Key Remote Buffer Overflow Vulnerability (CAN-2002-0656.) This vulnerability affects many machines worldwide; therefore the analysis and exploitation of this vulnerability is of high priority. The vulnerability arises when users are allowed to modify a size variable that is used in a memory copy function. The users have the ability to change this size value to whatever they please, causing more data to be copied. The buffer that overflows is found on the heap and is exploitable due to the data structure the buffer is found in. Because this vulnerability is in the heapspace there may or may not be an exploitation technique that works across multiple platforms. The technique presented in this case study works across multiple platforms and does not rely on any operating system (OS) specific memory allocation routines.

xlockmore User Supplied Format String Vulnerability

Abstract: This chapter discusses a case study of an xlockmore user supplied format string vulnerability. It starts with an overview of common vulnerabilities and exposures (CVE)-2000-0763 format string vulnerability. A format string vulnerability exists in the xlockmore program written by David Bagley. The program xlock contains a format string vulnerability when using the –d option of the application. Due to the fact that xlock is setuid root on Open Berkeley Software distribution (BSD), gaining local root access is possible. Other Unixes may not have xlock setuid root, therefore not yielding root when exploited. The xlockmore vulnerability is a simple example of a format string vulnerability using the syslog function. To exploit this vulnerability, the return address must be overwritten on the stack using the %n technique. An exploit for this vulnerability on OpenBSD written by Sinan Eren is shown in the chapter.