Issues (66)

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.

src/Magestead/Helper/Config.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 namespace Magestead\Helper;
2
3
use Magestead\Exceptions\MissingComposerHomeException;
4
use Magestead\Exceptions\MissingConfigFileException;
5
use Symfony\Component\Console\Output\OutputInterface;
6
use Symfony\Component\Yaml\Exception\ParseException;
7
use Symfony\Component\Yaml\Parser;
8
9
class Config
10
{
11
    protected $_config;
12
13
    protected $_projectPath;
14
15
    /**
16
     * @var OutputInterface
17
     */
18
    private $output;
19
20
    /**
21
     * Config constructor.
22
     * @param OutputInterface $output
23
     */
24
    public function __construct(OutputInterface $output)
25
    {
26
        $this->_projectPath = getcwd();
27
        $this->output = $output;
28
    }
29
30
    /**
31
     * @param $name
32
     * @return mixed
33
     */
34
    function __get($name)
0 ignored issues
show
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
35
    {
36
        $this->_config = $this->getConfigFile($this->output);
37
        return $this->_config['magestead']['apps']['mba_12345'][$name];
38
    }
39
40
    /**
41
     * @param OutputInterface $output
42
     * @return bool|mixed
43
     */
44
    protected function getConfigFile(OutputInterface $output)
45
    {
46
        $config = new Parser();
47
        try {
48
            return $config->parse($this->readConfigFile());
49
        } catch (ParseException $e) {
50
            $output->writeln('<error>Unable to parse the config file</error>');
51
        }
52
53
        return false;
54
    }
55
56
    /**
57
     * @return string
58
     * @throws MissingConfigFileException
59
     */
60
    protected function readConfigFile()
61
    {
62
        if (!file_exists($this->_projectPath . '/magestead.yaml')) {
63
            throw new MissingConfigFileException('No config file was found, are you in the project root?');
64
        }
65
66
        return file_get_contents($this->_projectPath . '/magestead.yaml');
67
    }
68
69
    /**
70
     * Find the composer home directory on non Mac environments (experimental)
71
     *
72
     * @return string
73
     * @throws MissingComposerHomeException
74
     */
75
    public function getComposerHomeDir()
76
    {
77
        $composerConfig = shell_exec('composer config --list --global | grep home');
78
79
        if (is_null($composerConfig)) {
80
            throw new MissingComposerHomeException('Composer home directory is not found. Do you have it installed?');
81
        }
82
83
        return trim(str_replace('[home] ', '', $composerConfig));
84
    }
85
}
86