Issues (31)

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.

lib/Cerbere/Parser/Yaml.php (2 issues)

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
 * Drush Cerbere command line tools.
5
 * Copyright (C) 2015 - Sebastien Malot <[email protected]>
6
 *
7
 * This program is free software; you can redistribute it and/or modify
8
 * it under the terms of the GNU General Public License as published by
9
 * the Free Software Foundation; either version 2 of the License, or
10
 * (at your option) any later version.
11
 *
12
 * This program is distributed in the hope that it will be useful,
13
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
14
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
15
 * GNU General Public License for more details.
16
 *
17
 * You should have received a copy of the GNU General Public License along
18
 * with this program; if not, write to the Free Software Foundation, Inc.,
19
 * 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
20
 */
21
22
namespace Cerbere\Parser;
23
24
use Cerbere\Model\Project;
25
use Symfony\Component\Yaml\Exception\ParseException;
26
27
/**
28
 * Class Yaml
29
 * @package Cerbere\Parser
30
 */
31
class Yaml extends Ini
32
{
33
    /**
34
     * @var Project
35
     */
36
    protected $project;
37
38
    /**
39
     *
40
     */
41
    public function __construct()
42
    {
43
44
    }
45
46
    /**
47
     * @return string
48
     */
49
    public function getCode()
50
    {
51
        return 'yaml';
52
    }
53
54
    /**
55
     * @return Project[]
56
     */
57
    public function getProjects()
58
    {
59
        return array($this->getProject());
60
    }
61
62
    /**
63
     * @return Project
64
     */
65
    public function getProject()
66
    {
67
        return $this->project;
68
    }
69
70
    /**
71
     * @param string $content
72
     * @param string $filename
73
     */
74 View Code Duplication
    public function processContent($content, $filename = null)
0 ignored issues
show
This method seems to be duplicated in your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
75
    {
76
        $data = $this->parseContent($content);
77
        $data += array('project' => basename($filename, '.info.yml'), 'version' => '');
78
79
        $project = new Project($data['project'], $data['core'], $data['version']);
80
        $project->setDetails($data);
81
82
        if (!empty($filename)) {
83
            $project->setFilename(realpath($filename));
84
        }
85
86
        $this->project = $project;
87
    }
88
89
    /**
90
     * @param string $content
91
     * @return array
92
     * @throws ParseException
93
     */
94
    protected function parseContent($content)
95
    {
96
        $parsed_info = \Symfony\Component\Yaml\Yaml::parse($content);
97
98
        $missing_keys = array_diff($this->getRequiredKeys(), array_keys($parsed_info));
99
100
        if (!empty($missing_keys)) {
101
            throw new ParseException('Missing required keys (' . implode(', ', $missing_keys) . ')');
102
        }
103
104
        return $parsed_info;
0 ignored issues
show
Bug Best Practice introduced by
The return type of return $parsed_info; (string|array|stdClass) is incompatible with the return type of the parent method Cerbere\Parser\Ini::parseContent of type array.

If you return a value from a function or method, it should be a sub-type of the type that is given by the parent type f.e. an interface, or abstract method. This is more formally defined by the Lizkov substitution principle, and guarantees that classes that depend on the parent type can use any instance of a child type interchangably. This principle also belongs to the SOLID principles for object oriented design.

Let’s take a look at an example:

class Author {
    private $name;

    public function __construct($name) {
        $this->name = $name;
    }

    public function getName() {
        return $this->name;
    }
}

abstract class Post {
    public function getAuthor() {
        return 'Johannes';
    }
}

class BlogPost extends Post {
    public function getAuthor() {
        return new Author('Johannes');
    }
}

class ForumPost extends Post { /* ... */ }

function my_function(Post $post) {
    echo strtoupper($post->getAuthor());
}

Our function my_function expects a Post object, and outputs the author of the post. The base class Post returns a simple string and outputting a simple string will work just fine. However, the child class BlogPost which is a sub-type of Post instead decided to return an object, and is therefore violating the SOLID principles. If a BlogPost were passed to my_function, PHP would not complain, but ultimately fail when executing the strtoupper call in its body.

Loading history...
105
    }
106
107
    /**
108
     * @return string[]
109
     */
110
    protected function getRequiredKeys()
111
    {
112
        return array('type', 'core', 'name');
113
    }
114
115
    /**
116
     * @param string $filename
117
     */
118
    public function processFile($filename)
119
    {
120
        $content = file_get_contents($filename);
121
122
        $this->processContent($content, $filename);
123
    }
124
125
    /**
126
     * @parser string $filename
127
     * @return boolean
128
     */
129
    public function supportedFile($filename)
130
    {
131
        return preg_match('/\.info\.yml$/i', $filename) > 0;
132
    }
133
}
134
135