Issues (71)

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.

src/WidgetValidationBase.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
namespace Drupal\entity_browser;
4
5
use Drupal\Core\Plugin\ContainerFactoryPluginInterface;
6
use Drupal\Core\Plugin\PluginBase;
7
use Drupal\Core\TypedData\DataDefinitionInterface;
8
use Drupal\Core\TypedData\TypedDataManagerInterface;
9
use Symfony\Component\DependencyInjection\ContainerInterface;
10
use Symfony\Component\Validator\ConstraintViolationList;
11
12
/**
13
 * Base implementation for widget validation plugins.
14
 */
15
abstract class WidgetValidationBase extends PluginBase implements WidgetValidationInterface, ContainerFactoryPluginInterface {
16
17
  /**
18
   * Plugin label.
19
   *
20
   * @var string
21
   */
22
  protected $label;
23
24
  /**
25
   * The Typed Data Manager service.
26
   *
27
   * @var \Drupal\Core\TypedData\TypedDataManagerInterface
28
   */
29
  protected $typedDataManager;
30
31
  public function __construct(array $configuration, $plugin_id, $plugin_definition, TypedDataManagerInterface $typed_data_manager) {
32
    $plugin_definition += [
33
      'constraint' => NULL,
34
    ];
35
    parent::__construct($configuration, $plugin_id, $plugin_definition);
36
    $this->typedDataManager = $typed_data_manager;
37
  }
38
39
  /**
40
   * {@inheritdoc}
41
   */
42
  public static function create(ContainerInterface $container, array $configuration, $plugin_id, $plugin_definition) {
43
    return new static(
44
      $configuration,
45
      $plugin_id,
46
      $plugin_definition,
47
      $container->get('typed_data_manager')
48
    );
49
  }
50
51
  /**
52
   * {@inheritdoc}
53
   */
54
  public function defaultConfiguration() {
55
    return [];
56
  }
57
58
  /**
59
   * {@inheritdoc}
60
   */
61
  public function label() {
62
    $this->label;
63
  }
64
65
  /**
66
   * {@inheritdoc}
67
   */
68
  public function validate(array $entities, $options = []) {
69
    $plugin_definition = $this->getPluginDefinition();
70
    $data_definition = $this->getDataDefinition($plugin_definition['data_type'], $plugin_definition['constraint'], $options);
71
    return $this->validateDataDefinition($data_definition, $entities);
0 ignored issues
show
Bug Best Practice introduced by
The return type of return $this->validateDa...definition, $entities); (Symfony\Component\Valida...ConstraintViolationList) is incompatible with the return type declared by the interface Drupal\entity_browser\Wi...tionInterface::validate of type Symfony\Component\Valida...tViolationListInterface.

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...
72
  }
73
74
  /**
75
   * {@inheritdoc}
76
   */
77
  public function getConfiguration() {
78
    return $this->configuration;
79
  }
80
81
  /**
82
   * {@inheritdoc}
83
   */
84
  public function setConfiguration(array $configuration) {
85
    $this->configuration = $configuration;
86
  }
87
88
  /**
89
   * {@inheritdoc}
90
   */
91
  public function calculateDependencies() {
92
    return [];
93
  }
94
95
  /**
96
   * Gets a data definition and optionally adds a constraint.
97
   *
98
   * @param string $data_type
99
   *   The data type plugin ID, for which a constraint should be added.
100
   * @param string $constraint_name
101
   *   The name of the constraint to add, i.e. its plugin id.
102
   * @param $options
103
   *   Array of options needed by the constraint validator.
104
   *
105
   * @return \Drupal\Core\TypedData\DataDefinitionInterface
106
   *   A data definition object for the given data type.
107
   */
108
  protected function getDataDefinition($data_type, $constraint_name = NULL, $options = []) {
109
    $data_definition = $this->typedDataManager->createDataDefinition($data_type);
110
    if ($constraint_name) {
0 ignored issues
show
Bug Best Practice introduced by
The expression $constraint_name of type string|null is loosely compared to true; this is ambiguous if the string can be empty. You might want to explicitly use !== null instead.

In PHP, under loose comparison (like ==, or !=, or switch conditions), values of different types might be equal.

For string values, the empty string '' is a special case, in particular the following results might be unexpected:

''   == false // true
''   == null  // true
'ab' == false // false
'ab' == null  // false

// It is often better to use strict comparison
'' === false // false
'' === null  // false
Loading history...
111
      $data_definition->addConstraint($constraint_name, $options);
112
    }
113
    return $data_definition;
114
  }
115
116
  /**
117
   * Creates and validates instances of typed data for each Entity.
118
   *
119
   * @param \Drupal\Core\TypedData\DataDefinitionInterface $data_definition
120
   *   The data definition generated from ::getDataDefinition().
121
   * @param array $entities
122
   *   An array of Entities to validate the definition against
123
   *
124
   * @return \Symfony\Component\Validator\ConstraintViolationListInterface
125
   *   A list of violations.
126
   */
127
  protected function validateDataDefinition(DataDefinitionInterface $data_definition, array $entities) {
128
    $violations = new ConstraintViolationList();
129
    foreach ($entities as $entity) {
130
      $validation_result = $this->typedDataManager->create($data_definition, $entity)->validate();
131
      $violations->addAll($validation_result);
132
    }
133
134
    return $violations;
135
  }
136
}
137