Issues (233)

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/Utils/Code/Xmlparse.php (4 issues)

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
namespace Wechat\Utils\Code;
3
4
use Wechat\Utils\Code\ErrorCode;
5
6
/**
7
 * XMLParse class
8
 *
9
 * 提供提取消息格式中的密文及生成回复消息格式的接口.
10
 */
11
class XMLParse
12
{
13
14
    /**
15
     * 提取出xml数据包中的加密消息
16
     *
17
     * @param string $xmltext 待提取的xml字符串
18
     *
19
     * @return string 提取出的加密消息字符串
20
     */
21
    public function extract($xmltext)
22
    {
23
        try {
24
            $object     = simplexml_load_string($xmltext, 'SimpleXMLElement', LIBXML_NOCDATA);
25
            $encrypt    = $object->Encrypt;
0 ignored issues
show
The property Encrypt does not seem to exist in SimpleXMLElement.

An attempt at access to an undefined property has been detected. This may either be a typographical error or the property has been renamed but there are still references to its old name.

If you really want to allow access to undefined properties, you can define magic methods to allow access. See the php core documentation on Overloading.

Loading history...
26
            $tousername = $object->ToUserName;
0 ignored issues
show
The property ToUserName does not seem to exist in SimpleXMLElement.

An attempt at access to an undefined property has been detected. This may either be a typographical error or the property has been renamed but there are still references to its old name.

If you really want to allow access to undefined properties, you can define magic methods to allow access. See the php core documentation on Overloading.

Loading history...
27
28
            return [0, $encrypt, $tousername];
29
        } catch (Exception $e) {
0 ignored issues
show
The class Wechat\Utils\Code\Exception does not exist. Did you forget a USE statement, or did you not list all dependencies?

Scrutinizer analyzes your composer.json/composer.lock file if available to determine the classes, and functions that are defined by your dependencies.

It seems like the listed class was neither found in your dependencies, nor was it found in the analyzed files in your repository. If you are using some other form of dependency management, you might want to disable this analysis.

Loading history...
30
            //print $e . "\n";
0 ignored issues
show
Unused Code Comprehensibility introduced by
50% of this comment could be valid code. Did you maybe forget this after debugging?

Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.

The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.

This check looks for comments that seem to be mostly valid code and reports them.

Loading history...
31
            return [ErrorCode::$ParseXmlError, null, null];
32
        }
33
    }
34
35
    /**
36
     * 生成xml消息
37
     *
38
     * @param string $encrypt   加密后的消息密文
39
     * @param string $signature 安全签名
40
     * @param string $timestamp 时间戳
41
     * @param string $nonce     随机字符串
42
     */
43
    public function generate($encrypt, $signature, $timestamp, $nonce)
44
    {
45
        $format = "<xml>
46
<Encrypt><![CDATA[%s]]></Encrypt>
47
<MsgSignature><![CDATA[%s]]></MsgSignature>
48
<TimeStamp>%s</TimeStamp>
49
<Nonce><![CDATA[%s]]></Nonce>
50
</xml>";
51
52
        return sprintf($format, $encrypt, $signature, $timestamp, $nonce);
53
    }
54
}
55