Issues (101)

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.

Console/Component/User/ListUsersCommand.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
2
3
declare(strict_types=1);
4
5
/*
6
 * This file is part of the Explicit Architecture POC,
7
 * which is created on top of the Symfony Demo application.
8
 *
9
 * (c) Herberto Graça <[email protected]>
10
 *
11
 * For the full copyright and license information, please view the LICENSE
12
 * file that was distributed with this source code.
13
 */
14
15
namespace Acme\App\Presentation\Console\Component\User;
16
17
use Acme\App\Core\Component\User\Application\Repository\UserRepositoryInterface;
18
use Acme\App\Core\Component\User\Domain\User\User;
19
use Swift_Mailer;
20
use Symfony\Component\Console\Command\Command;
21
use Symfony\Component\Console\Input\InputInterface;
22
use Symfony\Component\Console\Input\InputOption;
23
use Symfony\Component\Console\Output\BufferedOutput;
24
use Symfony\Component\Console\Output\OutputInterface;
25
use Symfony\Component\Console\Style\SymfonyStyle;
26
27
/**
28
 * A console command that lists all the existing users.
29
 *
30
 * To use this command, open a terminal window, enter into your project directory
31
 * and execute the following:
32
 *
33
 *     $ php bin/console app:list-users
34
 *
35
 * See https://symfony.com/doc/current/cookbook/console/console_command.html
36
 * For more advanced uses, commands can be defined as services too. See
37
 * https://symfony.com/doc/current/console/commands_as_services.html
38
 *
39
 * @author Javier Eguiluz <[email protected]>
40
 * @author Herberto Graca <[email protected]>
41
 */
42
class ListUsersCommand extends Command
43
{
44
    /**
45
     * A good practice is to use the 'app:' prefix to group all your custom application commands.
46
     *
47
     * @var string
48
     */
49
    protected static $defaultName = 'app:list-users';
50
51
    /**
52
     * @var Swift_Mailer
53
     */
54
    private $mailer;
55
56
    /**
57
     * @var string
58
     */
59
    private $emailSender;
60
61
    /**
62
     * @var UserRepositoryInterface
63
     */
64
    private $userRepository;
65
66
    public function __construct(
67
        Swift_Mailer $mailer,
68
        string $defaultFromEmailAddress,
69
        UserRepositoryInterface $userRepository
70
    ) {
71
        parent::__construct();
72
73
        $this->mailer = $mailer;
74
        $this->emailSender = $defaultFromEmailAddress;
75
        $this->userRepository = $userRepository;
76
    }
77
78
    /**
79
     * {@inheritdoc}
80
     */
81
    protected function configure(): void
82
    {
83
        $this
84
            ->setDescription('Lists all the existing users')
85
            ->setHelp(<<<'HELP'
86
                The <info>%command.name%</info> command lists all the users registered in the application:
0 ignored issues
show
This code did not parse for me. Apparently, there is an error somewhere around this line:

Syntax error, unexpected EOF
Loading history...
87
88
                  <info>php %command.full_name%</info>
89
90
                By default the command only displays the 50 most recent users. Set the number of
91
                results to display with the <comment>--max-results</comment> option:
92
93
                  <info>php %command.full_name%</info> <comment>--max-results=2000</comment>
94
95
                In addition to displaying the user list, you can also send this information to
96
                the email address specified in the <comment>--send-to</comment> option:
97
98
                  <info>php %command.full_name%</info> <comment>[email protected]</comment>
99
100
                HELP
101
            )
102
            // commands can optionally define arguments and/or options (mandatory and optional)
103
            // see https://symfony.com/doc/current/components/console/console_arguments.html
104
            ->addOption('max-results', null, InputOption::VALUE_OPTIONAL, 'Limits the number of users listed', 50)
105
            ->addOption('send-to', null, InputOption::VALUE_OPTIONAL, 'If set, the result is sent to the given email address');
106
    }
107
108
    /**
109
     * This method is executed after initialize(). It usually contains the logic
110
     * to execute to complete this command task.
111
     */
112
    protected function execute(InputInterface $input, OutputInterface $output): void
113
    {
114
        $maxResults = $input->getOption('max-results');
115
        $allUsers = $this->userRepository->findAll(['id' => 'DESC'], $maxResults);
116
117
        // Doctrine query returns an array of objects and we need an array of plain arrays
118
        $usersAsPlainArrays = array_map(function (User $user) {
119
            return [
120
                $user->getId(),
121
                $user->getFullName(),
122
                $user->getUsername(),
123
                $user->getEmail(),
124
                implode(', ', $user->getRoles()),
125
            ];
126
        }, $allUsers);
127
128
        // In your console commands you should always use the regular output type,
129
        // which outputs contents directly in the console window. However, this
130
        // command uses the BufferedOutput type instead, to be able to get the output
131
        // contents before displaying them. This is needed because the command allows
132
        // to send the list of users via email with the '--send-to' option
133
        $bufferedOutput = new BufferedOutput();
134
        $io = new SymfonyStyle($input, $bufferedOutput);
135
        $io->table(
136
            ['ID', 'Full Name', 'Username', 'Email', 'Roles'],
137
            $usersAsPlainArrays
138
        );
139
140
        // instead of just displaying the table of users, store its contents in a variable
141
        $usersAsATable = $bufferedOutput->fetch();
142
        $output->write($usersAsATable);
143
144
        if (null !== $email = $input->getOption('send-to')) {
145
            $this->sendReport($usersAsATable, $email);
146
        }
147
    }
148
149
    /**
150
     * Sends the given $contents to the $recipient email address.
151
     */
152
    private function sendReport(string $contents, string $recipient): void
153
    {
154
        // See https://symfony.com/doc/current/cookbook/email/email.html
155
        $message = $this->mailer->createMessage()
156
            ->setSubject(sprintf('app:list-users report (%s)', date('Y-m-d H:i:s')))
157
            ->setFrom($this->emailSender)
158
            ->setTo($recipient)
159
            ->setBody($contents, 'text/plain');
160
161
        $this->mailer->send($message);
162
    }
163
}
164