Issues (32)

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.

Manager/TokenManagerInterface.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
2
3
namespace Yokai\SecurityTokenBundle\Manager;
4
5
use DateTime;
6
use Yokai\SecurityTokenBundle\Entity\Token;
7
use Yokai\SecurityTokenBundle\Exception\TokenExpiredException;
8
use Yokai\SecurityTokenBundle\Exception\TokenNotFoundException;
9
use Yokai\SecurityTokenBundle\Exception\TokenConsumedException;
10
11
/**
12
 * A token manager is the entry point to deal with tokens.
13
 *
14
 * @author Yann Eugoné <[email protected]>
15
 */
16
interface TokenManagerInterface
17
{
18
    /**
19
     * Get a token instance.
20
     *
21
     * @param string $purpose The token purpose
22
     * @param string $value   The token value
23
     *
24
     * @return Token
25
     *
26
     * @throws TokenNotFoundException if the token cannot be found
27
     * @throws TokenExpiredException if the token is expired
28
     * @throws TokenConsumedException if the token is consumed
29
     */
30
    public function get($purpose, $value);
31
32
    /**
33
     * Create a token.
34
     *
35
     * @param string $purpose The token purpose
36
     * @param mixed  $user    The user to associate to the token
37
     * @param array  $payload Some additional payload for the token
38
     *
39
     * @return Token
40
     */
41
    public function create($purpose, $user, array $payload = []);
42
43
    /**
44
     * @param Token         $token
45
     * @param DateTime|null $at
46
     *
47
     * @deprecated since version 2.2 and will be removed in 3.0
48
     */
49
    public function setUsed(Token $token, DateTime $at = null);
50
51
    /**
52
     * Consume a token.
53
     *
54
     * @param Token         $token The token to consume
55
     * @param DateTime|null $at    The date/time at which the token was consumed (defaults to now)
56
     */
57
    public function consume(Token $token, DateTime $at = null);
0 ignored issues
show
For interfaces and abstract methods it is generally a good practice to add a @return annotation even if it is just @return void or @return null, so that implementors know what to do in the overridden method.

For interface and abstract methods, it is impossible to infer the return type from the immediate code. In these cases, it is generally advisible to explicitly annotate these methods with a @return doc comment to communicate to implementors of these methods what they are expected to return.

Loading history...
58
59
    /**
60
     * Get the user associated to a token.
61
     *
62
     * @param Token $token The token
63
     *
64
     * @return mixed
65
     */
66
    public function getUser(Token $token);
67
}
68