Issues in cdr.php (v3.0) - Issues in v3.0 - iNextrix/ASTPP - Measure and Improve Code Quality continuously with Scrutinizer

Issues (4511)

Security Analysis not enabled

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.

freeswitch/fs/cdr.php (4 issues)

Labels

Severity

Minor 4

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

<?php
###############################################################################
# ASTPP - Open Source VoIP Billing Solution
#
# Copyright (C) 2016 iNextrix Technologies Pvt. Ltd.
# Samir Doshi <[email protected]>
# ASTPP Version 3.0 and above
# License https://www.gnu.org/licenses/agpl-3.0.html
#
# This program is free software: you can redistribute it and/or modify
# it under the terms of the GNU Affero General Public License as
# published by the Free Software Foundation, either version 3 of the
# License, or (at your option) any later version.
# 
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU Affero General Public License for more details.
# 
# You should have received a copy of the GNU Affero General Public License
# along with this program.  If not, see <http://www.gnu.org/licenses/>.
###############################################################################

define('ENVIRONMENT', 'production');
if (defined('ENVIRONMENT'))
{
	switch (ENVIRONMENT)
	{
		case 'development':
//			error_reporting(E_ALL);

			error_reporting(E_ERROR|E_WARNING|E_PARSE);
		break;
	
		case 'testing':
		case 'production':
			error_reporting(0);
		break;

		default:
			exit('The application environment is not set correctly.');
	}
}

include ("lib/astpp.db.php");
include ("lib/astpp.logger.php");
include ("lib/astpp.lib.php");
include ("lib/astpp.constants.php");
include ("lib/astpp.cdr.php");

//Define db object
$db = new db();

//Get default configuration
$lib = new lib();
$config = $lib->get_configurations($db);

//Set default decimal points 
$decimal_points = ($config['decimal_points'] <= 0)?4:$config['decimal_points'];

//Define logger object
$logger = new logger($lib);

if(isset($_SERVER["CONTENT_TYPE"]) && $_SERVER["CONTENT_TYPE"] == "application/json") {

	$db->run("SET NAMES utf8");
	$data = json_decode(file_get_contents("php://input"),true);
	//error_log(print_r($data,true));

	$logger->log(print_r($data,true));
	if($data['variables']['calltype']== "CALLINGCARD"){
    		if(isset($data['variables']['originating_leg_uuid']))
    		{
	     		process_cdr($data,$db,$logger,$decimal_points);
    		}
    	}else{
        	process_cdr($data,$db,$logger,$decimal_points);
    	}
}

//$db->cleanup();

?>



1			<?php
2			###############################################################################
3			# ASTPP - Open Source VoIP Billing Solution
4			#
5			# Copyright (C) 2016 iNextrix Technologies Pvt. Ltd.
6			# Samir Doshi <[email protected]>
7			# ASTPP Version 3.0 and above
8			# License https://www.gnu.org/licenses/agpl-3.0.html
9			#
10			# This program is free software: you can redistribute it and/or modify
11			# it under the terms of the GNU Affero General Public License as
12			# published by the Free Software Foundation, either version 3 of the
13			# License, or (at your option) any later version.
14			#
15			# This program is distributed in the hope that it will be useful,
16			# but WITHOUT ANY WARRANTY; without even the implied warranty of
17			# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
18			# GNU Affero General Public License for more details.
19			#
20			# You should have received a copy of the GNU Affero General Public License
21			# along with this program. If not, see <http://www.gnu.org/licenses/>.
22			###############################################################################
23
24			define('ENVIRONMENT', 'production');
25			if (defined('ENVIRONMENT'))
26			{
27			switch (ENVIRONMENT)
28			{
29			case 'development':
30			// error_reporting(E_ALL);
			0 ignored issues – show Unused Code Comprehensibility introduced 2016-10-16 16:00 UTC by Report Bug Copy Issue Report Show Similar Issues like this `50%` of this comment could be valid code. Did you maybe forget this after debugging? Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
31			error_reporting(E_ERROR\|E_WARNING\|E_PARSE);
32			break;
33
34			case 'testing':
35			case 'production':
36			error_reporting(0);
37			break;
38
39			default:
40			exit('The application environment is not set correctly.');
41			}
42			}
43
44			include ("lib/astpp.db.php");
45			include ("lib/astpp.logger.php");
46			include ("lib/astpp.lib.php");
47			include ("lib/astpp.constants.php");
48			include ("lib/astpp.cdr.php");
49
50			//Define db object
51			$db = new db();
52
53			//Get default configuration
54			$lib = new lib();
55			$config = $lib->get_configurations($db);
56
57			//Set default decimal points
58			$decimal_points = ($config['decimal_points'] <= 0)?4:$config['decimal_points'];
59
60			//Define logger object
61			$logger = new logger($lib);
62
63			if(isset($_SERVER["CONTENT_TYPE"]) && $_SERVER["CONTENT_TYPE"] == "application/json") {
64
65			$db->run("SET NAMES utf8");
66			$data = json_decode(file_get_contents("php://input"),true);
67			//error_log(print_r($data,true));
			0 ignored issues – show Unused Code Comprehensibility introduced 2016-10-16 16:00 UTC by Report Bug Copy Issue Report Show Similar Issues like this `80%` of this comment could be valid code. Did you maybe forget this after debugging? Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
68			$logger->log(print_r($data,true));
69			if($data['variables']['calltype']== "CALLINGCARD"){
70			if(isset($data['variables']['originating_leg_uuid']))
71			{
72			process_cdr($data,$db,$logger,$decimal_points);
73			}
74			}else{
75			process_cdr($data,$db,$logger,$decimal_points);
76			}
77			}
78
79			//$db->cleanup();
			0 ignored issues – show Unused Code Comprehensibility introduced 2016-10-16 16:00 UTC by Report Bug Copy Issue Report Show Similar Issues like this `84%` of this comment could be valid code. Did you maybe forget this after debugging? Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it. The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production. This check looks for comments that seem to be mostly valid code and reports them. Loading history...
80			?>
			0 ignored issues – show Best Practice introduced 2016-10-16 16:00 UTC by Report Bug Copy Issue Report Show Similar Issues like this It is not recommended to use PHP's closing tag `?>` in files other than templates. Using a closing tag in PHP files that only contain PHP code is not recommended as you might accidentally add whitespace after the closing tag which would then be output by PHP. This can cause severe problems, for example headers cannot be sent anymore. A simple precaution is to leave off the closing tag as it is not required, and it also has no negative effects whatsoever. Loading history...
81

iNextrix / ASTPP

Issues (4511)

Security Analysis not enabled

freeswitch/fs/cdr.php (4 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like