Issues (19)

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.

ValidatorAdapters/CodeIgniterFormValidator.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 Rocket\UI\Forms\ValidatorAdapters;
2
3
class CodeIgniterFormValidator implements ValidatorInterface
4
{
5
    /**
6
     * @var \Form_validation
7
     */
8
    protected $validator;
9
10
    /**
11
     * {@inheritdoc}
12
     */
13
    public function __construct($validator, $data, $defaults)
14
    {
15
        $this->validator = $validator;
16
        $validator->set_form_values($data);
17
        foreach ($defaults as $field => $value) {
18
            $validator->set_default($field, $value);
19
        }
20
    }
21
22
    /**
23
     * {@inheritdoc}
24
     */
25
    public function getValue($name, $default = '')
26
    {
27
        return $this->validator->set_value($name, $default);
28
    }
29
30
    /**
31
     * {@inheritdoc}
32
     */
33
    public function hasError($name)
34
    {
35
        return $this->validator->has_error($name);
36
    }
37
38
    /**
39
     * {@inheritdoc}
40
     */
41
    public function getErrors($name)
42
    {
43
        return $this->validator->get_error($name);
44
    }
45
46
    /**
47
     * {@inheritdoc}
48
     */
49
    protected function getRules($name)
50
    {
51
        return $this->validator->getRules($name);
52
    }
53
54
    /**
55
     * {@inheritdoc}
56
     */
57
    public function isRequired($name)
58
    {
59
        if (!empty($this->validator->_field_required[$name])) {
60
            return $this->validator->_field_required[$name];
61
        } else {
62
            return false;
63
        }
64
    }
65
66
    /**
67
     * {@inheritdoc}
68
     */
69
    public static function supports($object)
70
    {
71
        return $object instanceof \Form_validation;
0 ignored issues
show
The class Form_validation 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...
72
    }
73
}
74