Issues (87)

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/Aop/Framework/DeclareErrorInterceptor.php (1 issue)

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
declare(strict_types=1);
4
/*
5
 * Go! AOP framework
6
 *
7
 * @copyright Copyright 2013, Lisachenko Alexander <[email protected]>
8
 *
9
 * This source file is subject to the license that is bundled
10
 * with this source code in the file LICENSE.
11
 */
12
13
namespace Go\Aop\Framework;
14
15
use Closure;
16
use Go\Aop\Intercept\FieldAccess;
17
use Go\Aop\Intercept\Joinpoint;
18
19
/**
20
 * Interceptor to dynamically trigger an user notice/warning/error on method call
21
 *
22
 * This interceptor can be used as active replacement for the "deprecated" tag or to notify about
23
 * probable issues with specific method.
24
 */
25
final class DeclareErrorInterceptor extends AbstractInterceptor
26
{
27
    /**
28
     * Error message to show for this interceptor
29
     */
30
    protected string $message;
0 ignored issues
show
This code did not parse for me. Apparently, there is an error somewhere around this line:

Syntax error, unexpected T_STRING, expecting T_FUNCTION or T_CONST
Loading history...
31
32
    /**
33
     * Default level of error
34
     */
35
    protected int $level;
36
37
    /**
38
     * Default constructor for interceptor
39
     */
40
    public function __construct(string $message, int $errorLevel, string $pointcutExpression)
41
    {
42
        $adviceMethod  = self::getDeclareErrorAdvice();
43
        $this->message = $message;
44
        $this->level   = $errorLevel;
45
        parent::__construct($adviceMethod, -256, $pointcutExpression);
46
    }
47
48
    /**
49
     * @inheritdoc
50
     */
51
    public static function unserializeAdvice(array $adviceData): Closure
52
    {
53
        return self::getDeclareErrorAdvice();
54
    }
55
56
    /**
57
     * @inheritdoc
58
     */
59
    public function invoke(Joinpoint $joinpoint)
60
    {
61
        if ($joinpoint instanceof FieldAccess) {
62
            $scope = $joinpoint->getScope();
63
            $name  = $joinpoint->getField()->getName();
64
            ($this->adviceMethod)($scope, $name, $this->message, $this->level);
65
        }
66
67
        return $joinpoint->proceed();
68
    }
69
70
    /**
71
     * Returns an advice
72
     */
73
    private static function getDeclareErrorAdvice(): Closure
74
    {
75
        static $adviceMethod;
76
77
        if ($adviceMethod === null) {
78
            $adviceMethod = function (string $scope, string $property, string $message, int $level = E_USER_NOTICE) {
79
                $message = vsprintf(
80
                    '[AOP Declare Error]: %s has an error: "%s"',
81
                    [
82
                        $scope . '->' . $property,
83
                        $message
84
                    ]
85
                );
86
                trigger_error($message, $level);
87
            };
88
        }
89
90
        return $adviceMethod;
91
    }
92
}
93