Issues (118)

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.

Messaging/Model/MessageMetaInterface.php (4 issues)

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
/*
4
 * This file is part of the MilioooMessageBundle package.
5
 *
6
 * (c) Michiel boeckaert <[email protected]>
7
 * This source file is subject to the MIT license that is bundled
8
 * with this source code in the file LICENSE.
9
 */
10
11
namespace Miliooo\Messaging\Model;
12
13
use Miliooo\Messaging\User\ParticipantInterface;
14
use Miliooo\Messaging\ValueObjects\ReadStatus;
15
16
/**
17
 * Interface for the message meta
18
 *
19
 * @author Michiel Boeckaert <[email protected]>
20
 */
21
interface MessageMetaInterface extends BuilderInterface
22
{
23
24
    /**
25
     * The participant has never read the message
26
     */
27
    const READ_STATUS_NEVER_READ = 0;
28
29
    /**
30
     * The participant has read the message but marked it as unread
31
     */
32
    const READ_STATUS_MARKED_UNREAD = 1;
33
34
    /**
35
     * The participant has read the message
36
     */
37
    const READ_STATUS_READ = 2;
38
39
40
    /**
41
     * Sets the participant to the message meta
42
     *
43
     * @param ParticipantInterface $participant The participant we add to the meta
44
     */
45
    public function setParticipant(ParticipantInterface $participant);
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...
46
47
    /**
48
     * Gets the participant from the meta
49
     *
50
     * @return ParticipantInterface The participant from the meta
51
     */
52
    public function getParticipant();
53
54
    /**
55
     * Sets the read status of the message for the given participant.
56
     *
57
     * @param ReadStatus $readStatus
58
     */
59
    public function setReadStatus(ReadStatus $readStatus);
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...
60
61
    /**
62
     * Gets the read status of the message for the participant of this meta
63
     *
64
     * @return integer one of the read statuses constants
65
     */
66
    public function getReadStatus();
67
68
    /**
69
     * Sets the message this message meta belongs to
70
     *
71
     * @param MessageInterface $message The message this meta belongs to
72
     */
73
    public function setMessage(MessageInterface $message);
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...
74
75
    /**
76
     * Gets the message
77
     *
78
     * @return MessageInterface The message this meta belongs to
79
     */
80
    public function getMessage();
81
82
83
84
    /**
85
     * Gets the previous read status of a message.
86
     *
87
     * Since we update the read status before we display the messages to the user we need to check the previous read
88
     * status to see if a message is a new read or not
89
     *
90
     * @return $boolean
0 ignored issues
show
The doc-type $boolean could not be parsed: Unknown type name "$boolean" at position 0. (view supported doc-types)

This check marks PHPDoc comments that could not be parsed by our parser. To see which comment annotations we can parse, please refer to our documentation on supported doc-types.

Loading history...
91
     */
92
    public function getPreviousReadStatus();
93
}
94