Issues (1626)

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.

phpsysinfo/includes/to/class.MBInfo.inc.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
 * MBInfo TO class
4
 *
5
 * PHP version 5
6
 *
7
 * @category  PHP
8
 * @package   PSI_TO
9
 * @author    Michael Cramer <[email protected]>
10
 * @copyright 2009 phpSysInfo
11
 * @license   http://opensource.org/licenses/gpl-2.0.php GNU General Public License
12
 * @version   SVN: $Id: class.MBInfo.inc.php 253 2009-06-17 13:07:50Z bigmichi1 $
13
 * @link      http://phpsysinfo.sourceforge.net
14
 */
15
 /**
16
 * MBInfo TO class
17
 *
18
 * @category  PHP
19
 * @package   PSI_TO
20
 * @author    Michael Cramer <[email protected]>
21
 * @copyright 2009 phpSysInfo
22
 * @license   http://opensource.org/licenses/gpl-2.0.php GNU General Public License
23
 * @version   Release: 3.0
24
 * @link      http://phpsysinfo.sourceforge.net
25
 */
26
class MBInfo
0 ignored issues
show
Coding Style Compatibility introduced by
PSR1 recommends that each class must be in a namespace of at least one level to avoid collisions.

You can fix this by adding a namespace to your class:

namespace YourVendor;

class YourClass { }

When choosing a vendor namespace, try to pick something that is not too generic to avoid conflicts with other libraries.

Loading history...
27
{
28
    /**
29
     * array with SensorDevices for temperatures
30
     *
31
     * @see SensorDevice
32
     *
33
     * @var Array
34
     */
35
    private $_mbTemp = array();
36
37
    /**
38
     * array with SensorDevices for fans
39
     *
40
     * @see SensorDevice
41
     *
42
     * @var Array
43
     */
44
    private $_mbFan = array();
45
46
    /**
47
     * array with SensorDevices for voltages
48
     *
49
     * @see SensorDevice
50
     *
51
     * @var Array
52
     */
53
    private $_mbVolt = array();
54
55
    /**
56
     * array with SensorDevices for power
57
     *
58
     * @see SensorDevice
59
     *
60
     * @var Array
61
     */
62
    private $_mbPower = array();
63
64
    /**
65
     * array with SensorDevices for apmers
66
     *
67
     * @see SensorDevice
68
     *
69
     * @var Array
70
     */
71
    private $_mbCurrent = array();
72
73
    /**
74
     * Returns $_mbFan.
75
     *
76
     * @see System::$_mbFan
77
     *
78
     * @return Array
79
     */
80
    public function getMbFan()
81
    {
82
        return $this->_mbFan;
83
    }
84
85
    /**
86
     * Sets $_mbFan.
87
     *
88
     * @param SensorDevice $mbFan fan device
89
     *
90
     * @see System::$_mbFan
91
     *
92
     * @return Void
93
     */
94
    public function setMbFan($mbFan)
95
    {
96
        array_push($this->_mbFan, $mbFan);
97
    }
98
99
    /**
100
     * Returns $_mbTemp.
101
     *
102
     * @see System::$_mbTemp
103
     *
104
     * @return Array
105
     */
106
    public function getMbTemp()
107
    {
108
        return $this->_mbTemp;
109
    }
110
111
    /**
112
     * Sets $_mbTemp.
113
     *
114
     * @param Sensor $mbTemp temp device
115
     *
116
     * @see System::$_mbTemp
117
     *
118
     * @return Void
119
     */
120
    public function setMbTemp($mbTemp)
121
    {
122
        array_push($this->_mbTemp, $mbTemp);
123
    }
124
125
    /**
126
     * Returns $_mbVolt.
127
     *
128
     * @see System::$_mbVolt
129
     *
130
     * @return Array
131
     */
132
    public function getMbVolt()
133
    {
134
        return $this->_mbVolt;
135
    }
136
137
    /**
138
     * Sets $_mbVolt.
139
     *
140
     * @param Sensor $mbVolt voltage device
141
     *
142
     * @see System::$_mbVolt
143
     *
144
     * @return Void
145
     */
146
    public function setMbVolt($mbVolt)
147
    {
148
        array_push($this->_mbVolt, $mbVolt);
149
    }
150
151
    /**
152
     * Returns $_mbPower.
153
     *
154
     * @see System::$_mbPower
155
     *
156
     * @return Array
157
     */
158
    public function getMbPower()
159
    {
160
        return $this->_mbPower;
161
    }
162
163
    /**
164
     * Sets $_mbPower.
165
     *
166
     * @param Sensor $mbPower power device
167
     *
168
     * @see System::$_mbPower
169
     *
170
     * @return Void
171
     */
172
    public function setMbPower($mbPower)
173
    {
174
        array_push($this->_mbPower, $mbPower);
175
    }
176
    /**
177
     * Returns $_mbCurrent.
178
     *
179
     * @see System::$_mbCurrent
180
     *
181
     * @return Array
182
     */
183
    public function getMbCurrent()
184
    {
185
        return $this->_mbCurrent;
186
    }
187
188
    /**
189
     * Sets $_mbCurrent.
190
     *
191
     * @param Sensor $mbCurrent current device
192
     *
193
     * @see System::$_mbCurrent
194
     *
195
     * @return Void
196
     */
197
    public function setMbCurrent($mbCurrent)
198
    {
199
        array_push($this->_mbCurrent, $mbCurrent);
200
    }
201
}
202