Issues (104)

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/Search/ClientInterface.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
namespace As3\Modlr\Search;
4
5
use As3\Modlr\Metadata\EntityMetadata;
6
use As3\Modlr\Metadata\Interfaces\SearchMetadataFactoryInterface;
7
use As3\Modlr\Persister\PersisterInterface;
8
use As3\Modlr\Persister\RecordSetInterface;
9
10
/**
11
 * Defines the service implementation for searching for (and modifying) models in the search layer.
12
 *
13
 * @author Jacob Bare <[email protected]>
14
 */
15
interface ClientInterface
16
{
17
    /**
18
     * Gets the key name for this search client.
19
     * Is used to uniquely indentify this search type by the search manager.
20
     * Is also the type key for the search metadata layer.
21
     *
22
     * @return  string
23
     */
24
    public function getClientKey();
25
26
    /**
27
     * Gets the search metadata factory for creating SearchInterface instances.
28
     *
29
     * @return  SearchMetadataFactoryInterface
30
     */
31
    public function getSearchMetadataFactory();
32
33
    /**
34
     * Queries/searchs for records for the specified type.
35
     * Uses the search query, runs the search, and then loads the full models from the persistence layer.
36
     *
37
     * @todo    Implement sorting and pagination (limit/skip).
38
     * @param   EntityMetadata      $metadata
39
     * @param   array               $criteria
40
     * @param   PersisterInterface  $persister
41
     * @return  RecordSetInterface
42
     */
43
    public function query(EntityMetadata $metadata, array $criteria, PersisterInterface $persister);
44
45
    /**
46
     * Returns a set of autocomplete results for a model type, attribute key, and search value.
47
     *
48
     * @param   string  $typeKey
0 ignored issues
show
There is no parameter named $typeKey. Was it maybe removed?

This check looks for PHPDoc comments describing methods or function parameters that do not exist on the corresponding method or function.

Consider the following example. The parameter $italy is not defined by the method finale(...).

/**
 * @param array $germany
 * @param array $island
 * @param array $italy
 */
function finale($germany, $island) {
    return "2:1";
}

The most likely cause is that the parameter was removed, but the annotation was not.

Loading history...
49
     * @param   string  $attributeKey
50
     * @param   string  $searchValue
51
     * @return  AutocompleteResult[]
52
     */
53
    public function autocomplete(EntityMetadata $metadata, $attributeKey, $searchValue);
54
}
55