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/Token/AbstractToken.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
/**
4
 * AbstractToken.php
5
 *
6
 * @date 28.03.2015 2:49:42
7
 * @copyright Sklyarov Alexey <[email protected]>
8
 */
9
10
namespace Sufir\Calc\Token;
11
12
use InvalidArgumentException;
13
use Sufir\Calc\Token;
14
15
/**
16
 * AbstractToken
17
 *
18
 * Description of AbstractToken
19
 *
20
 * @author Sklyarov Alexey <[email protected]>
21
 * @package Sufir\Calc\Token
22
 */
23
abstract class AbstractToken implements Token
24
{
25
    /**
26
     *
27
     * @var mixed
28
     */
29
    protected $value;
30
31
    /**
32
     *
33
     * @param string $value
34
     * @return \Sufir\Calc\Token\AbstractToken
0 ignored issues
show
Comprehensibility Best Practice introduced by
Adding a @return annotation to constructors is generally not recommended as a constructor does not have a meaningful return value.

Adding a @return annotation to a constructor is not recommended, since a constructor does not have a meaningful return value.

Please refer to the PHP core documentation on constructors.

Loading history...
35
     */
36 107
    public function __construct($value)
37
    {
38 107
        if (!static::validate($value)) {
39 59
            throw new InvalidArgumentException(
40 59
                "Wrong value «{$value}» for " . __CLASS__
41 59
            );
42
        }
43
44 48
        $this->value = $this->sanitize($value);
45
46 48
        return $this;
47
    }
48
49
    /**
50
     *
51
     * @return mixed
52
     */
53 37
    public function getValue()
54
    {
55 37
        return $this->value;
56
    }
57
58
    /**
59
     *
60
     * @return boolean
61
     */
62 34
    public function isNumber()
63
    {
64 34
        return ($this instanceof NumberToken);
65
    }
66
67
    /**
68
     *
69
     * @return boolean
70
     */
71 34
    public function isFunction()
72
    {
73 34
        return ($this instanceof FunctionToken);
74
    }
75
76
    /**
77
     *
78
     * @return boolean
79
     */
80 33
    public function isOperator()
81
    {
82 33
        return ($this instanceof OperatorToken);
83
    }
84
85
    /**
86
     *
87
     * @return boolean
88
     */
89 34
    public function isBracket()
90
    {
91 34
        return ($this instanceof BracketToken);
92
    }
93
94
    /**
95
     *
96
     * @return boolean
97
     */
98 34
    public function isVariable()
99
    {
100 34
        return ($this instanceof VariableToken);
101
    }
102
103
    /**
104
     *
105
     * @return boolean
106
     */
107 34
    public function isDelimiter()
108
    {
109 34
        return ($this instanceof DelimiterToken);
110
    }
111
112
    /**
113
     *
114
     * @return string
115
     */
116 21
    public function __toString()
117
    {
118 21
        return strval($this->getValue());
119
    }
120
121
    /**
122
     *
123
     * @param string $value
124
     * @return mixed
125
     */
126
    abstract protected function sanitize($value);
127
}
128