Issues (35)

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.

debug/Event.php (1 issue)

Labels
Severity

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 namespace nyx\diagnostics\debug;
2
3
// External dependencies
4
use nyx\events;
5
6
// Internal dependencies
7
use nyx\diagnostics\definitions;
8
9
/**
10
 * Debug Event
11
 *
12
 * Note: Setting the Exception within a diagnostics\definitions\Events::DEBUG_EXCEPTION_AFTER Event has no effect
13
 * whatsoever.
14
 *
15
 * @package     Nyx\Diagnostics\Debug
16
 * @version     0.1.0
17
 * @author      Michal Chojnacki <[email protected]>
18
 * @copyright   2012-2016 Nyx Dev Team
19
 * @link        http://docs.muyo.io/nyx/diagnostics/debug.html
20
 */
21
class Event extends events\Event
22
{
23
    /**
24
     * @var \Exception  The Exception which is being handled.
25
     */
26
    private $exception;
27
28
    /**
29
     * @var Handler     The Handler which emitted this Event.
30
     */
31
    private $handler;
32
33
    /**
34
     * {@inheritDoc}
35
     *
36
     * @param   \Exception      $exception  The Exception which is being handled.
37
     * @param   Handler         $handler    The Handler which emitted this Event.
38
     */
39
    public function __construct(\Exception $exception, Handler $handler, $name = null)
40
    {
41
        $this->exception = $exception;
42
        $this->handler   = $handler;
43
44
        parent::__construct($name);
45
    }
46
47
    /**
48
     * Returns the Exception which is being handled.
49
     *
50
     * @return  \Exception
51
     */
52
    public function getException()
53
    {
54
        return $this->exception;
55
    }
56
57
    /**
58
     * Sets the Exception to be handled.
59
     *
60
     * @param   \Exception  $exception
61
     * @return  $this
62
     */
63
    public function setException(\Exception $exception)
64
    {
65
        // Setting the Exception after it's already been handled makes no sense. This might potentially lead to
66
        // confusion in the future as we are not throwing an Exception on our own for this in order not to mess
67
        // up things while already within an Exception Handler context.
68
        if ($this->getName() !== definitions\Events::DEBUG_EXCEPTION_AFTER) {
0 ignored issues
show
Consider using $this->name. There is an issue with getName() and APC-enabled PHP versions.
Loading history...
69
            $this->exception = $exception;
70
        }
71
72
        return $this;
73
    }
74
75
    /**
76
     * Returns the Handler which emitted this Event.
77
     *
78
     * @return  Handler
79
     */
80
    public function getHandler()
81
    {
82
        return $this->handler;
83
    }
84
}
85