Issues (133)

Security Analysis    no vulnerabilities found

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.

docs/examples/MessageCallback.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
 * Threema message callback listener. (example).
4
 *
5
 * @package ThreemaGateway
6
 * @author rugk
7
 * @copyright Copyright (c) 2015-2016 rugk
8
 * @license MIT
9
 */
10
11
/**
12
 * Listeners for custom activity when a text message is received.
13
 */
14
class ThreemaGateway_Listener_MessageCallback
15
{
16
    /**
17
     * Receives text messages.
18
     *
19
     * @param ThreemaGateway_Handler_Action_Callback      $handler
20
     * @param Threema\MsgApi\Helpers\ReceiveMessageResult $receiveResult
21
     * @param Threema\MsgApi\Messages\ThreemaMessage      $threemaMsg
22
     * @param array|string                                $output        [$logType, $debugLog, $publicLog]
23
     * @param bool                                        $saveMessage
24
     * @param bool                                        $debugMode
25
     *
26
     * @throws XenForo_Exception
27
     */
28
    public static function testCallbackPreSave(ThreemaGateway_Handler_Action_Callback $handler,
29
                                        Threema\MsgApi\Helpers\ReceiveMessageResult $receiveResult,
30
                                        Threema\MsgApi\Messages\ThreemaMessage $threemaMsg,
31
                                        &$output,
32
                                        &$saveMessage,
33
                                        $debugMode)
0 ignored issues
show
The parameter $debugMode is not used and could be removed.

This check looks from parameters that have been defined for a function or method, but which are not used in the method body.

Loading history...
34
    {
35
        // for performance reasons you should check first, whether the message
36
        // meets your requirements respectively needs to be handled by the
37
        // listener.
38
        if ($threemaMsg->getText() != 'test message') {
39
            // IMPORTANT: Do not return false as this would cause all other
40
            // registered listeners to stop! You may not want to do that.
41
            return;
42
        }
43
44
        // first check whether message has already been saved to prevent replay attacks
45
        $handler->assertNoReplayAttack($receiveResult->getMessageId());
46
47
        // it is useful to add some logging messages for easier debugging
48
        $handler->addLog($output, 'Message will not be saved to database!');
49
50
        // here you can do something with your text messages
51
        $saveMessage = false; // e.g. prevent saving!
52
    }
53
54
    /**
55
     * Receives text messages after saving them.
56
     *
57
     * @param ThreemaGateway_Handler_Action_Callback      $handler
58
     * @param Threema\MsgApi\Helpers\ReceiveMessageResult $receiveResult
59
     * @param Threema\MsgApi\Messages\ThreemaMessage      $threemaMsg
60
     * @param array|string                                $output        [$logType, $debugLog, $publicLog]
61
     * @param bool                                        $debugMode
62
     */
63
    public static function testCallbackPostSave(ThreemaGateway_Handler_Action_Callback $handler,
64
                                        Threema\MsgApi\Helpers\ReceiveMessageResult $receiveResult,
0 ignored issues
show
The parameter $receiveResult is not used and could be removed.

This check looks from parameters that have been defined for a function or method, but which are not used in the method body.

Loading history...
65
                                        Threema\MsgApi\Messages\ThreemaMessage $threemaMsg,
0 ignored issues
show
The parameter $threemaMsg is not used and could be removed.

This check looks from parameters that have been defined for a function or method, but which are not used in the method body.

Loading history...
66
                                        &$output,
67
                                        $messageSaved,
68
                                        $debugMode)
0 ignored issues
show
The parameter $debugMode is not used and could be removed.

This check looks from parameters that have been defined for a function or method, but which are not used in the method body.

Loading history...
69
    {
70
        if (!$messageSaved) {
71
            // this should only be shown when testCallbackPreSave has been executed
72
            // or another listener prevented saving of the data.
73
            $handler->addLog($output, 'This is the message, which has not been saved!');
74
        }
75
    }
76
}
77