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/ThreadMetaInterface.php (6 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
15
/**
16
 * The interface for the threadmeta class
17
 *
18
 * @author Michiel Boeckaert <[email protected]>
19
 */
20
interface ThreadMetaInterface extends BuilderInterface
21
{
22
    const STATUS_ACTIVE = 1;
23
    const STATUS_ARCHIVED = 2;
24
25
    /**
26
     * Gets the unique id of the thread meta
27
     *
28
     * @return integer
29
     */
30
    public function getId();
31
32
    /**
33
     * Gets the participant of the thread meta
34
     *
35
     * @return ParticipantInterface
36
     */
37
    public function getParticipant();
38
39
    /**
40
     * Sets the participant of the thread meta
41
     *
42
     * @param ParticipantInterface $participant The participant
43
     */
44
    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...
45
46
    /**
47
     * Sets the thread for this thread meta
48
     *
49
     * @param ThreadInterface $thread The thread this meta belongs to
50
     */
51
    public function setThread(ThreadInterface $thread);
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...
52
53
    /**
54
     * Gets the thread for this thread meta
55
     *
56
     * @return ThreadInterface the thread this meta belongs to
57
     */
58
    public function getThread();
59
60
    /**
61
     * Gets the status of the given thread for the participant of the threadMeta.
62
     *
63
     * @return integer one of the status constants
64
     */
65
    public function getStatus();
66
67
    /**
68
     * Sets the status of the thread for the given participant.
69
     *
70
     * @param integer $status
71
     */
72
    public function setStatus($status);
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...
73
74
    /**
75
     * Gets the datetime when the participant has written his last message for
76
     * the given thread
77
     *
78
     * @return \DateTime
79
     */
80
    public function getLastParticipantMessageDate();
81
82
    /**
83
     * Sets the datetime when the participant has written his last message for the given thread
84
     *
85
     * @param \DateTime $dateTime DateTime of participant's last message
86
     */
87
    public function setLastParticipantMessageDate(\DateTime $dateTime);
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...
88
89
    /**
90
     * Gets the date time of the last message written by another participant
91
     *
92
     * @return \DateTime datetime of the last message written by another participant
93
     */
94
    public function getLastMessageDate();
95
96
    /**
97
     * Sets the date of the last message written by another participant
98
     *
99
     * @param \DateTime $lastMessageDate datetime of the last message by another participant
100
     */
101
    public function setLastMessageDate(\DateTime $lastMessageDate);
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...
102
103
    /**
104
     * Gets the number of unread messages for the participant from the given thread.
105
     *
106
     * @return integer The number of unread messages from the thread for the given participant
107
     */
108
    public function getUnreadMessageCount();
109
110
    /**
111
     * Sets the number of unread messages for the participant from the given thread.
112
     *
113
     * @param integer $unreadCount The number of unread messages from the thread for the given participant
114
     */
115
    public function setUnreadMessageCount($unreadCount);
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...
116
}
117