Issues (32)

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.

src/Whoops/Handler/XmlResponseHandler.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
 * Whoops - php errors for cool kids
4
 * @author Filipe Dobreira <http://github.com/filp>
5
 */
6
7
namespace Whoops\Handler;
8
9
use SimpleXMLElement;
10
use Whoops\Exception\Formatter;
11
12
/**
13
 * Catches an exception and converts it to an XML
14
 * response. Additionally can also return exception
15
 * frames for consumption by an API.
16
 */
17
class XmlResponseHandler extends Handler
18
{
19
    /**
20
     * @var bool
21
     */
22
    private $returnFrames = false;
23
24
    /**
25
     * @param  bool|null  $returnFrames
26
     * @return bool|static
27
     */
28 1 View Code Duplication
    public function addTraceToOutput($returnFrames = null)
0 ignored issues
show
This method seems to be duplicated in your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
29
    {
30 1
        if (func_num_args() == 0) {
31 1
            return $this->returnFrames;
32
        }
33
34
        $this->returnFrames = (bool) $returnFrames;
35
        return $this;
36
    }
37
38
    /**
39
     * @return int
40
     */
41 1
    public function handle()
42
    {
43
        $response = [
44 1
            'error' => Formatter::formatExceptionAsDataArray(
45 1
                $this->getInspector(),
46 1
                $this->addTraceToOutput()
0 ignored issues
show
It seems like $this->addTraceToOutput() targeting Whoops\Handler\XmlRespon...ler::addTraceToOutput() can also be of type this<Whoops\Handler\XmlResponseHandler>; however, Whoops\Exception\Formatt...tExceptionAsDataArray() does only seem to accept boolean, maybe add an additional type check?

This check looks at variables that are passed out again to other methods.

If the outgoing method call has stricter type requirements than the method itself, an issue is raised.

An additional type check may prevent trouble.

Loading history...
47 1
            ),
48 1
        ];
49
50 1
        echo self::toXml($response);
51
52 1
        return Handler::QUIT;
53
    }
54
55
    /**
56
     * @return string
57
     */
58 1
    public function contentType()
59
    {
60 1
        return 'application/xml';
61
    }
62
63
    /**
64
     * @param  SimpleXMLElement  $node Node to append data to, will be modified in place
65
     * @param  array|\Traversable $data
66
     * @return SimpleXMLElement  The modified node, for chaining
67
     */
68 1
    private static function addDataToNode(\SimpleXMLElement $node, $data)
69
    {
70 1
        assert(is_array($data) || $data instanceof Traversable);
0 ignored issues
show
The class Whoops\Handler\Traversable does not exist. Did you forget a USE statement, or did you not list all dependencies?

This error could be the result of:

1. Missing dependencies

PHP Analyzer uses your composer.json file (if available) to determine the dependencies of your project and to determine all the available classes and functions. It expects the composer.json to be in the root folder of your repository.

Are you sure this class is defined by one of your dependencies, or did you maybe not list a dependency in either the require or require-dev section?

2. Missing use statement

PHP does not complain about undefined classes in ìnstanceof checks. For example, the following PHP code will work perfectly fine:

if ($x instanceof DoesNotExist) {
    // Do something.
}

If you have not tested against this specific condition, such errors might go unnoticed.

Loading history...
71
72 1
        foreach ($data as $key => $value) {
73 1
            if (is_numeric($key)) {
74
                // Convert the key to a valid string
75
                $key = "unknownNode_". (string) $key;
76
            }
77
78
            // Delete any char not allowed in XML element names
79 1
            $key = preg_replace('/[^a-z0-9\-\_\.\:]/i', '', $key);
80
81 1
            if (is_array($value)) {
82 1
                $child = $node->addChild($key);
83 1
                self::addDataToNode($child, $value);
84 1
            } else {
85 1
                $value = str_replace('&', '&amp;', print_r($value, true));
86 1
                $node->addChild($key, $value);
87
            }
88 1
        }
89
90 1
        return $node;
91
    }
92
93
    /**
94
     * The main function for converting to an XML document.
95
     *
96
     * @param  array|\Traversable $data
97
     * @return string            XML
98
     */
99 1
    private static function toXml($data)
100
    {
101 1
        assert(is_array($data) || $data instanceof Traversable);
0 ignored issues
show
The class Whoops\Handler\Traversable does not exist. Did you forget a USE statement, or did you not list all dependencies?

This error could be the result of:

1. Missing dependencies

PHP Analyzer uses your composer.json file (if available) to determine the dependencies of your project and to determine all the available classes and functions. It expects the composer.json to be in the root folder of your repository.

Are you sure this class is defined by one of your dependencies, or did you maybe not list a dependency in either the require or require-dev section?

2. Missing use statement

PHP does not complain about undefined classes in ìnstanceof checks. For example, the following PHP code will work perfectly fine:

if ($x instanceof DoesNotExist) {
    // Do something.
}

If you have not tested against this specific condition, such errors might go unnoticed.

Loading history...
102
103 1
        $node = simplexml_load_string("<?xml version='1.0' encoding='utf-8'?><root />");
104
105 1
        return self::addDataToNode($node, $data)->asXML();
106
    }
107
}
108