Issues (4)

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.

src/SoapServer.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 Afonso\Soapi;
4
5
use League\Pipeline\Pipeline;
6
use SoapServer as NativeSoapServer;
7
8
/**
9
 * A enhanced, drop-in replacement for PHP's native SoapServer class.
10
 *
11
 * This server includes input and output pipelines to aribtrarily modify
12
 * requests and responses.
13
 */
14
class SoapServer extends NativeSoapServer
15
{
16
    use ProcessesWithPipelines;
17
18
    /**
19
     * Creates and returns a new SoapServer with empty inbound and outbound
20
     * pipelines.
21
     *
22
     * @param   string|null $wsdl
23
     * @param   array       $options
24
     */
25
    public function __construct($wsdl, array $options = array())
26
    {
27
        parent::__construct($wsdl, $options);
28
29
        // initialize in and outbound pipelines
30
        $this->inboundPipeline = new Pipeline();
31
        $this->outboundPipeline = new Pipeline();
32
    }
33
34
    /**
35
     * Handles a SOAP request.
36
     *
37
     * This function delegates on PHP's native SoapServer handle(), but
38
     * processes the input XML through the inbound and outbound pipelines. This
39
     * allows for arbitrary manipulation of requests and responses, such as
40
     * encryption or logging.
41
     *
42
     * Just as the parent class, this function will fetch the input from the
43
     * POST data if none is passed as an argument. Likewise, it will return
44
     * nothing and output the response instead.
45
     *
46
     * @see     http://php.net/manual/en/soapserver.handle.php
47
     * @param   string|null $soapRequest
48
     */
49
    public function handle($soapRequest = null)
50
    {
51
        if (! $soapRequest) {
52
            $soapRequest = file_get_contents('php://input');
53
        }
54
55
        /*
56
         * Run the request XML through the inbound pipeline.
57
         */
58
        $soapRequest = $this->inboundPipeline->process($soapRequest);
59
60
        /*
61
         * Execute the request.
62
         */
63
        ob_start();
64
        parent::handle($soapRequest);
65
        $soapResponse = ob_get_clean();
66
67
        /*
68
         * Then run the response through the outbound pipeline.
69
         */
70
        $soapResponse = $this->outboundPipeline->process($soapResponse);
71
72
        /*
73
         * Output the response and we're done.
74
         */
75
        $this->outputResponse($soapResponse);
76
    }
77
78
    protected function outputResponse($soapResponse)
79
    {
80
        echo $soapResponse;
81
        header('Content-Type: text/xml; charset=utf8');
82
        header('Content-Length: ' . strlen($soapResponse));
83
        exit(0);
0 ignored issues
show
Coding Style Compatibility introduced by
The method outputResponse() contains an exit expression.

An exit expression should only be used in rare cases. For example, if you write a short command line script.

In most cases however, using an exit expression makes the code untestable and often causes incompatibilities with other libraries. Thus, unless you are absolutely sure it is required here, we recommend to refactor your code to avoid its usage.

Loading history...
84
    }
85
}
86