Issues (3)

Security Analysis    no request data  

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.

src/GeneralEncoder.php (2 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
 * Created by PhpStorm.
4
 * User: claudio
5
 * Date: 17/09/15
6
 * Time: 14.42
7
 * This program is free software; you can redistribute it and/or
8
 * modify it under the terms of the GNU General Public License
9
 * as published by the Free Software Foundation; either version 2
10
 * of the License, or (at your option) any later version.
11
 * This program is distributed in the hope that it will be useful,
12
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
13
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
14
 * GNU General Public License for more details.
15
 * You should have received a copy of the GNU General Public License
16
 * along with this program; if not, write to the Free Software
17
 * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA.
18
 */
19
20
namespace it\thecsea\api_reflection;
21
22
/**
23
 * Class GeneralEncoder
24
 * @package it\thecsea\api_reflection
25
 * @author Claudio Cardinale <[email protected]>
26
 * @copyright 2015 Claudio Cardinale
27
 * @version 1.0.0
28
 */
29
class GeneralEncoder
30
{
31
    const MATRIX = "matrix";
32
    const TEXT = "text";
33
    const GENERAL_RETURN = "generalReturn";
34
35
    /**
36
     * Encode the return of each method into a string
37
     * @param mixed $methodReturn return of method called by reflection
38
     * @return string
39
     */
40
    public function stringEncode($methodReturn)
41
    {
42
        ob_start();
43
        print_r($methodReturn);
44
        return ob_get_clean();
45
    }
46
47
    /**
48
     * Encode the return of each method into a associative matrix
49
     * @param mixed $methodReturn return of method called by reflection
50
     * @return array
51
     */
52
    public function matrixEncode($methodReturn)
53
    {
54
        return self::encodeData($methodReturn);
55
    }
56
57
    /**
58
     * Encode a complex/simple data into an array with information for each element
59
     * @param $data
60
     * @param $name
61
     * @return string
62
     * @see encodeElement
63
     */
64
    final static protected function encodeData($data, $name = self::GENERAL_RETURN){
0 ignored issues
show
As per PSR2, the static declaration should come after the visibility declaration.
Loading history...
65
        //encoding
66
        if(is_array($data)){
67
            $tmp = array();
68
            foreach($data as $key=>$value){
69
                $tmp[] = self::encodeData($value, $key);
70
            }
71
            return self::encodeElement($tmp, $name, self::MATRIX);
72
        }else{
73
            return self::encodeElement(self::TEXT, $name, $data);
74
        }
75
    }
76
77
    /**
78
     * encode an element (can be a complex element such as an array) into a array with name and type information
79
     * @param mixed $value
80
     * @param string $name
81
     * @param string $type
82
     * @return array
83
     */
84
    final static protected function encodeElement($value, $name = "", $type = self::TEXT)
0 ignored issues
show
As per PSR2, the static declaration should come after the visibility declaration.
Loading history...
85
    {
86
        return array("type"=>$type, "name"=>$name, "value"=>$value);
87
    }
88
}