Issues (4069)

Security Analysis    not enabled

This project does not seem to handle request data directly as such no vulnerable execution paths were found.

  Cross-Site Scripting
Cross-Site Scripting enables an attacker to inject code into the response of a web-request that is viewed by other users. It can for example be used to bypass access controls, or even to take over other users' accounts.
  File Exposure
File Exposure allows an attacker to gain access to local files that he should not be able to access. These files can for example include database credentials, or other configuration files.
  File Manipulation
File Manipulation enables an attacker to write custom data to files. This potentially leads to injection of arbitrary code on the server.
  Object Injection
Object Injection enables an attacker to inject an object into PHP code, and can lead to arbitrary code execution, file exposure, or file manipulation attacks.
  Code Injection
Code Injection enables an attacker to execute arbitrary code on the server.
  Response Splitting
Response Splitting can be used to send arbitrary responses.
  File Inclusion
File Inclusion enables an attacker to inject custom files into PHP's file loading mechanism, either explicitly passed to include, or for example via PHP's auto-loading mechanism.
  Command Injection
Command Injection enables an attacker to inject a shell command that is execute with the privileges of the web-server. This can be used to expose sensitive data, or gain access of your server.
  SQL Injection
SQL Injection enables an attacker to execute arbitrary SQL code on your database server gaining access to user data, or manipulating user data.
  XPath Injection
XPath Injection enables an attacker to modify the parts of XML document that are read. If that XML document is for example used for authentication, this can lead to further vulnerabilities similar to SQL Injection.
  LDAP Injection
LDAP Injection enables an attacker to inject LDAP statements potentially granting permission to run unauthorized queries, or modify content inside the LDAP tree.
  Header Injection
  Other Vulnerability
This category comprises other attack vectors such as manipulating the PHP runtime, loading custom extensions, freezing the runtime, or similar.
  Regex Injection
Regex Injection enables an attacker to execute arbitrary code in your PHP process.
  XML Injection
XML Injection enables an attacker to read files on your local filesystem including configuration files, or can be abused to freeze your web-server process.
  Variable Injection
Variable Injection enables an attacker to overwrite program variables with custom data, and can lead to further vulnerabilities.
Unfortunately, the security analysis is currently not available for your project. If you are a non-commercial open-source project, please contact support to gain access.

include/nusoap/class.soap_fault.php (1 issue)

Upgrade to new PHP Analysis Engine

These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more

1
<?php
2
3
/*
4
5
Modification information for LGPL compliance
6
7
r57813 - 2010-08-19 10:34:44 -0700 (Thu, 19 Aug 2010) - kjing - Author: John Mertic <[email protected]>
8
    Bug 39085 - When loading the opposite search panel via ajax on the ListViews, call the index action instead of the ListView action to avoid touching pre-MVC code by accident.
9
10
r56990 - 2010-06-16 13:05:36 -0700 (Wed, 16 Jun 2010) - kjing - snapshot "Mango" svn branch to a new one for GitHub sync
11
12
r56989 - 2010-06-16 13:01:33 -0700 (Wed, 16 Jun 2010) - kjing - defunt "Mango" svn dev branch before github cutover
13
14
r55980 - 2010-04-19 13:31:28 -0700 (Mon, 19 Apr 2010) - kjing - create Mango (6.1) based on windex
15
16
r51719 - 2009-10-22 10:18:00 -0700 (Thu, 22 Oct 2009) - mitani - Converted to Build 3  tags and updated the build system 
17
18
r51634 - 2009-10-19 13:32:22 -0700 (Mon, 19 Oct 2009) - mitani - Windex is the branch for Sugar Sales 1.0 development
19
20
r50375 - 2009-08-24 18:07:43 -0700 (Mon, 24 Aug 2009) - dwong - branch kobe2 from tokyo r50372
21
22
r42807 - 2008-12-29 11:16:59 -0800 (Mon, 29 Dec 2008) - dwong - Branch from trunk/sugarcrm r42806 to branches/tokyo/sugarcrm
23
24
r13782 - 2006-06-06 10:58:55 -0700 (Tue, 06 Jun 2006) - majed - changes entry point code
25
26
r11115 - 2006-01-17 14:54:45 -0800 (Tue, 17 Jan 2006) - majed - add entry point validation
27
28
r8846 - 2005-10-31 11:01:12 -0800 (Mon, 31 Oct 2005) - majed - new version of nusoap
29
30
r5462 - 2005-05-25 13:50:11 -0700 (Wed, 25 May 2005) - majed - upgraded nusoap to .6.9
31
32
r573 - 2004-09-04 13:03:32 -0700 (Sat, 04 Sep 2004) - sugarclint - undoing copyrights added in inadvertantly.  --clint
33
34
r546 - 2004-09-03 11:49:38 -0700 (Fri, 03 Sep 2004) - sugarmsi - removed echo count
35
36
r354 - 2004-08-02 23:00:37 -0700 (Mon, 02 Aug 2004) - sugarjacob - Adding Soap
37
38
39
*/
40
41
42
if(!defined('sugarEntry') || !sugarEntry) die('Not A Valid Entry Point');
43
44
45
46
47
/**
48
* Contains information for a SOAP fault.
49
* Mainly used for returning faults from deployed functions
50
* in a server instance.
51
* @author   Dietrich Ayala <[email protected]>
52
53
* @access public
54
*/
55
class nusoap_fault extends nusoap_base {
56
	/**
57
	 * The fault code (client|server)
58
	 * @var string
59
	 * @access private
60
	 */
61
	var $faultcode;
62
	/**
63
	 * The fault actor
64
	 * @var string
65
	 * @access private
66
	 */
67
	var $faultactor;
68
	/**
69
	 * The fault string, a description of the fault
70
	 * @var string
71
	 * @access private
72
	 */
73
	var $faultstring;
74
	/**
75
	 * The fault detail, typically a string or array of string
76
	 * @var mixed
77
	 * @access private
78
	 */
79
	var $faultdetail;
80
81
	/**
82
	* constructor
83
    *
84
    * @param string $faultcode (SOAP-ENV:Client | SOAP-ENV:Server)
85
    * @param string $faultactor only used when msg routed between multiple actors
86
    * @param string $faultstring human readable error message
87
    * @param mixed $faultdetail detail, typically a string or array of string
88
	*/
89
	function nusoap_fault($faultcode,$faultactor='',$faultstring='',$faultdetail=''){
90
		parent::nusoap_base();
91
		$this->faultcode = $faultcode;
92
		$this->faultactor = $faultactor;
93
		$this->faultstring = $faultstring;
94
		$this->faultdetail = $faultdetail;
95
	}
96
97
	/**
98
	* serialize a fault
99
	*
100
	* @return	string	The serialization of the fault instance.
101
	* @access   public
102
	*/
103
	function serialize(){
104
		$ns_string = '';
105
		foreach($this->namespaces as $k => $v){
106
			$ns_string .= "\n  xmlns:$k=\"$v\"";
107
		}
108
		$return_msg =
109
			'<?xml version="1.0" encoding="'.$this->soap_defencoding.'"?>'.
110
			'<SOAP-ENV:Envelope SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"'.$ns_string.">\n".
111
				'<SOAP-ENV:Body>'.
112
				'<SOAP-ENV:Fault>'.
113
					$this->serialize_val($this->faultcode, 'faultcode').
114
					$this->serialize_val($this->faultactor, 'faultactor').
115
					$this->serialize_val($this->faultstring, 'faultstring').
116
					$this->serialize_val($this->faultdetail, 'detail').
117
				'</SOAP-ENV:Fault>'.
118
				'</SOAP-ENV:Body>'.
119
			'</SOAP-ENV:Envelope>';
120
		return $return_msg;
121
	}
122
}
123
124
/**
125
 * Backward compatibility
126
 */
127
class soap_fault extends nusoap_fault {
0 ignored issues
show
Coding Style Compatibility introduced by
PSR1 recommends that each class should be in its own file to aid autoloaders.

Having each class in a dedicated file usually plays nice with PSR autoloaders and is therefore a well established practice. If you use other autoloaders, you might not want to follow this rule.

Loading history...
128
}
129
130
131
?>