Issues (4141)

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.

PHPExcel/Shared/PDF/config/tcpdf_config_alt.php (4 issues)

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
// File name   : tcpdf_config.php
4
// Begin       : 2004-06-11
5
// Last Update : 2010-08-19
6
//
7
// Description : Alternative configuration file for TCPDF.
8
//
9
// Author: Nicola Asuni
10
//
11
// (c) Copyright:
12
//               Nicola Asuni
13
//               Tecnick.com s.r.l.
14
//               Via Della Pace, 11
15
//               09044 Quartucciu (CA)
16
//               ITALY
17
//               www.tecnick.com
18
//               [email protected]
19
//============================================================+
20
21
/**
22
 * Alternative configuration file for TCPDF.
23
 * @author Nicola Asuni
24
 * @copyright 2004-2010 Nicola Asuni - Tecnick.com S.r.l (www.tecnick.com) Via Della Pace, 11 - 09044 - Quartucciu (CA) - ITALY - www.tecnick.com - [email protected]
25
 * @package com.tecnick.tcpdf
26
 * @version 4.9.005
27
 * @link http://tcpdf.sourceforge.net
28
 * @license http://www.gnu.org/copyleft/lesser.html LGPL
29
 * @since 2004-10-27
30
 */
31
32
// DOCUMENT_ROOT fix for IIS Webserver
33
if ((!isset(DIR_RAIZ)) OR (empty(DIR_RAIZ))) {
0 ignored issues
show
This code did not parse for me. Apparently, there is an error somewhere around this line:

Syntax error, unexpected ')', expecting '['
Loading history...
Comprehensibility Best Practice introduced by
Using logical operators such as or instead of || is generally not recommended.

PHP has two types of connecting operators (logical operators, and boolean operators):

  Logical Operators Boolean Operator
AND - meaning and &&
OR - meaning or ||

The difference between these is the order in which they are executed. In most cases, you would want to use a boolean operator like &&, or ||.

Let’s take a look at a few examples:

// Logical operators have lower precedence:
$f = false or true;

// is executed like this:
($f = false) or true;


// Boolean operators have higher precedence:
$f = false || true;

// is executed like this:
$f = (false || true);

Logical Operators are used for Control-Flow

One case where you explicitly want to use logical operators is for control-flow such as this:

$x === 5
    or die('$x must be 5.');

// Instead of
if ($x !== 5) {
    die('$x must be 5.');
}

Since die introduces problems of its own, f.e. it makes our code hardly testable, and prevents any kind of more sophisticated error handling; you probably do not want to use this in real-world code. Unfortunately, logical operators cannot be combined with throw at this point:

// The following is currently a parse error.
$x === 5
    or throw new RuntimeException('$x must be 5.');

These limitations lead to logical operators rarely being of use in current PHP code.

Loading history...
34
	if(isset($_SERVER['SCRIPT_FILENAME'])) {
35
		DIR_RAIZ = str_replace( '\\', '/', substr($_SERVER['SCRIPT_FILENAME'], 0, 0-strlen($_SERVER['PHP_SELF'])));
36
	} elseif(isset($_SERVER['PATH_TRANSLATED'])) {
37
		DIR_RAIZ = str_replace( '\\', '/', substr(str_replace('\\\\', '\\', $_SERVER['PATH_TRANSLATED']), 0, 0-strlen($_SERVER['PHP_SELF'])));
38
	}	else {
39
		// define here your DOCUMENT_ROOT path if the previous fails
40
		DIR_RAIZ = '/var/www';
41
	}
42
}
43
44
// Automatic calculation for the following K_PATH_MAIN constant
45
$k_path_main = str_replace( '\\', '/', realpath(substr(dirname(__FILE__), 0, 0-strlen('config'))));
46
if (substr($k_path_main, -1) != '/') {
47
	$k_path_main .= '/';
48
}
49
50
/**
51
 * Installation path (/var/www/tcpdf/).
52
 * By default it is automatically calculated but you can also set it as a fixed string to improve performances.
53
 */
54
define ('K_PATH_MAIN', $k_path_main);
55
56
// Automatic calculation for the following K_PATH_URL constant
57
if (isset($_SERVER['HTTP_HOST']) AND (!empty($_SERVER['HTTP_HOST']))) {
0 ignored issues
show
Comprehensibility Best Practice introduced by
Using logical operators such as and instead of && is generally not recommended.

PHP has two types of connecting operators (logical operators, and boolean operators):

  Logical Operators Boolean Operator
AND - meaning and &&
OR - meaning or ||

The difference between these is the order in which they are executed. In most cases, you would want to use a boolean operator like &&, or ||.

Let’s take a look at a few examples:

// Logical operators have lower precedence:
$f = false or true;

// is executed like this:
($f = false) or true;


// Boolean operators have higher precedence:
$f = false || true;

// is executed like this:
$f = (false || true);

Logical Operators are used for Control-Flow

One case where you explicitly want to use logical operators is for control-flow such as this:

$x === 5
    or die('$x must be 5.');

// Instead of
if ($x !== 5) {
    die('$x must be 5.');
}

Since die introduces problems of its own, f.e. it makes our code hardly testable, and prevents any kind of more sophisticated error handling; you probably do not want to use this in real-world code. Unfortunately, logical operators cannot be combined with throw at this point:

// The following is currently a parse error.
$x === 5
    or throw new RuntimeException('$x must be 5.');

These limitations lead to logical operators rarely being of use in current PHP code.

Loading history...
58
	if(isset($_SERVER['HTTPS']) AND (!empty($_SERVER['HTTPS'])) AND strtolower($_SERVER['HTTPS'])!='off') {
0 ignored issues
show
Comprehensibility Best Practice introduced by
Using logical operators such as and instead of && is generally not recommended.

PHP has two types of connecting operators (logical operators, and boolean operators):

  Logical Operators Boolean Operator
AND - meaning and &&
OR - meaning or ||

The difference between these is the order in which they are executed. In most cases, you would want to use a boolean operator like &&, or ||.

Let’s take a look at a few examples:

// Logical operators have lower precedence:
$f = false or true;

// is executed like this:
($f = false) or true;


// Boolean operators have higher precedence:
$f = false || true;

// is executed like this:
$f = (false || true);

Logical Operators are used for Control-Flow

One case where you explicitly want to use logical operators is for control-flow such as this:

$x === 5
    or die('$x must be 5.');

// Instead of
if ($x !== 5) {
    die('$x must be 5.');
}

Since die introduces problems of its own, f.e. it makes our code hardly testable, and prevents any kind of more sophisticated error handling; you probably do not want to use this in real-world code. Unfortunately, logical operators cannot be combined with throw at this point:

// The following is currently a parse error.
$x === 5
    or throw new RuntimeException('$x must be 5.');

These limitations lead to logical operators rarely being of use in current PHP code.

Loading history...
59
		$k_path_url = 'https://';
60
	} else {
61
		$k_path_url = 'http://';
62
	}
63
	$k_path_url .= $_SERVER['HTTP_HOST'];
64
	$k_path_url .= str_replace( '\\', '/', substr(K_PATH_MAIN, (strlen(DIR_RAIZ) - 1)));
65
}
66
67
/**
68
 * URL path to tcpdf installation folder (http://localhost/tcpdf/).
69
 * By default it is automatically calculated but you can also set it as a fixed string to improve performances..
70
 */
71
define ('K_PATH_URL', $k_path_url);
72
73
/**
74
 * path for PDF fonts
75
 * use K_PATH_MAIN.'fonts/old/' for old non-UTF8 fonts
76
 */
77
define ('K_PATH_FONTS', K_PATH_MAIN.'fonts/');
78
79
/**
80
 * cache directory for temporary files (full path)
81
 */
82
define ('K_PATH_CACHE', K_PATH_MAIN.'cache/');
83
84
/**
85
 * cache directory for temporary files (url path)
86
 */
87
define ('K_PATH_URL_CACHE', K_PATH_URL.'cache/');
88
89
/**
90
 *images directory
91
 */
92
define ('K_PATH_IMAGES', K_PATH_MAIN.'images/');
93
94
/**
95
 * blank image
96
 */
97
define ('K_BLANK_IMAGE', K_PATH_IMAGES.'_blank.png');
98
99
/**
100
 * page format
101
 */
102
define ('PDF_PAGE_FORMAT', 'A4');
103
104
/**
105
 * page orientation (P=portrait, L=landscape)
106
 */
107
define ('PDF_PAGE_ORIENTATION', 'P');
108
109
/**
110
 * document creator
111
 */
112
define ('PDF_CREATOR', 'TCPDF');
113
114
/**
115
 * document author
116
 */
117
define ('PDF_AUTHOR', 'TCPDF');
118
119
/**
120
 * header title
121
 */
122
define ('PDF_HEADER_TITLE', 'TCPDF Example');
123
124
/**
125
 * header description string
126
 */
127
define ('PDF_HEADER_STRING', "by Nicola Asuni - Tecnick.com\nwww.tcpdf.org");
128
129
/**
130
 * image logo
131
 */
132
define ('PDF_HEADER_LOGO', 'tcpdf_logo.jpg');
133
134
/**
135
 * header logo image width [mm]
136
 */
137
define ('PDF_HEADER_LOGO_WIDTH', 30);
138
139
/**
140
 *  document unit of measure [pt=point, mm=millimeter, cm=centimeter, in=inch]
141
 */
142
define ('PDF_UNIT', 'mm');
143
144
/**
145
 * header margin
146
 */
147
define ('PDF_MARGIN_HEADER', 5);
148
149
/**
150
 * footer margin
151
 */
152
define ('PDF_MARGIN_FOOTER', 10);
153
154
/**
155
 * top margin
156
 */
157
define ('PDF_MARGIN_TOP', 27);
158
159
/**
160
 * bottom margin
161
 */
162
define ('PDF_MARGIN_BOTTOM', 25);
163
164
/**
165
 * left margin
166
 */
167
define ('PDF_MARGIN_LEFT', 15);
168
169
/**
170
 * right margin
171
 */
172
define ('PDF_MARGIN_RIGHT', 15);
173
174
/**
175
 * default main font name
176
 */
177
define ('PDF_FONT_NAME_MAIN', 'helvetica');
178
179
/**
180
 * default main font size
181
 */
182
define ('PDF_FONT_SIZE_MAIN', 10);
183
184
/**
185
 * default data font name
186
 */
187
define ('PDF_FONT_NAME_DATA', 'helvetica');
188
189
/**
190
 * default data font size
191
 */
192
define ('PDF_FONT_SIZE_DATA', 8);
193
194
/**
195
 * default monospaced font name
196
 */
197
define ('PDF_FONT_MONOSPACED', 'courier');
198
199
/**
200
 * ratio used to adjust the conversion of pixels to user units
201
 */
202
define ('PDF_IMAGE_SCALE_RATIO', 1.25);
203
204
/**
205
 * magnification factor for titles
206
 */
207
define('HEAD_MAGNIFICATION', 1.1);
208
209
/**
210
 * height of cell repect font height
211
 */
212
define('K_CELL_HEIGHT_RATIO', 1.25);
213
214
/**
215
 * title magnification respect main font size
216
 */
217
define('K_TITLE_MAGNIFICATION', 1.3);
218
219
/**
220
 * reduction factor for small font
221
 */
222
define('K_SMALL_RATIO', 2/3);
223
224
/**
225
 * set to true to enable the special procedure used to avoid the overlappind of symbols on Thai language
226
 */
227
define('K_THAI_TOPCHARS', true);
228
229
/**
230
 * if true allows to call TCPDF methods using HTML syntax
231
 * IMPORTANT: For security reason, disable this feature if you are printing user HTML content.
232
 */
233
define('K_TCPDF_CALLS_IN_HTML', true);
234
235
//============================================================+
236
// END OF FILE
237
//============================================================+
238