Issues (18)

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/ApigilityClient/Http/Response.php (6 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 ApigilityClient\Http;
3
4
use Zend\Http\Client as ZendHttpClient,
5
    Zend\Http\Response as ZendHttpResponse;
6
7
use ApigilityClient\Exception\RuntimeException,
8
    ApigilityClient\Http\Response\TriggerException,
9
    ApigilityClient\Http\Response\Content\HalJson,
10
    ApigilityClient\Http\Response\Content\EmptyContent;
11
12
final class Response
13
{
14
    /**
15
     * @var Zend\Http\Client
16
     */
17
    private $httpClient;
18
19
    /**
20
     * @var Zend\Http\Response
21
     */
22
    private $httpResponse;
23
24
    /**
25
     * @var ApiClient\Http\Response\Content\ContentInterface
26
     */
27
    private $strategyContent;
28
29
    /**
30
    * Construtor
31
    *
32
    * @param Zend\Http\Client   $client
33
    * @param Zend\Http\Response $response
34
    */
35
    public function __construct(ZendHttpClient $client, ZendHttpResponse $response)
36
    {
37
        $this->httpClient = $client;
0 ignored issues
show
Documentation Bug introduced by
It seems like $client of type object<Zend\Http\Client> is incompatible with the declared type object<ApigilityClient\Http\Zend\Http\Client> of property $httpClient.

Our type inference engine has found an assignment to a property that is incompatible with the declared type of that property.

Either this assignment is in error or the assigned type should be added to the documentation/type hint for that property..

Loading history...
38
        $this->httpResponse = $response;
0 ignored issues
show
Documentation Bug introduced by
It seems like $response of type object<Zend\Http\Response> is incompatible with the declared type object<ApigilityClient\Http\Zend\Http\Response> of property $httpResponse.

Our type inference engine has found an assignment to a property that is incompatible with the declared type of that property.

Either this assignment is in error or the assigned type should be added to the documentation/type hint for that property..

Loading history...
39
40
        try {
41
            $this->checkResponseStatus();
42
43
            if (204 == $this->httpResponse->getStatusCode()) {
44
                $this->strategyContent = new EmptyContent($this->httpClient, $this->httpResponse);
0 ignored issues
show
Documentation Bug introduced by
It seems like new \ApigilityClient\Htt...t, $this->httpResponse) of type object<ApigilityClient\H...e\Content\EmptyContent> is incompatible with the declared type object<ApigilityClient\H...ntent\ContentInterface> of property $strategyContent.

Our type inference engine has found an assignment to a property that is incompatible with the declared type of that property.

Either this assignment is in error or the assigned type should be added to the documentation/type hint for that property..

Loading history...
45
            } else {
46
                $contentType = $this->httpResponse->getHeaders()->get('Content-Type')->getFieldValue();
47
48
                switch (trim($contentType)) {
49
                    case HalJson::CONTENT_TYPE :
0 ignored issues
show
There must be no space before the colon in a CASE statement

As per the PSR-2 coding standard, there must not be a space in front of the colon in case statements.

switch ($selector) {
    case "A": //right
        doSomething();
        break;
    case "B" : //wrong
        doSomethingElse();
        break;
}

To learn more about the PSR-2 coding standard, please refer to the PHP-Fig.

Loading history...
50
                        $this->strategyContent = new HalJson($this->httpClient, $this->httpResponse);
0 ignored issues
show
Documentation Bug introduced by
It seems like new \ApigilityClient\Htt...t, $this->httpResponse) of type object<ApigilityClient\H...sponse\Content\HalJson> is incompatible with the declared type object<ApigilityClient\H...ntent\ContentInterface> of property $strategyContent.

Our type inference engine has found an assignment to a property that is incompatible with the declared type of that property.

Either this assignment is in error or the assigned type should be added to the documentation/type hint for that property..

Loading history...
51
                        break;
52
53
                    default :
0 ignored issues
show
There must be no space before the colon in a DEFAULT statement

As per the PSR-2 coding standard, there must not be a space in front of the colon in the default statement.

switch ($expr) {
    default : //wrong
        doSomething();
        break;
}

switch ($expr) {
    default: //right
        doSomething();
        break;
}

To learn more about the PSR-2 coding standard, please refer to the PHP-Fig.

Loading history...
54
                        $errorMessage = sprintf(
55
                            'The apigility server returned a mime type ("%s") that cannot be parsed by apigility client',
56
                            $contentType
57
                        );
58
59
                    return new TriggerException($this->httpClient, $this->httpResponse, $errorMessage);
60
                }
61
            }
62
63
        } catch (RuntimeException $e) {
64
	   throw $e;
65
        }
66
    }
67
68
    /**
69
     * Get the content
70
     *
71
     * @return mixed
72
     */
73
    public function getContent()
74
    {
75
        return $this->strategyContent->getContent();
76
    }
77
78
    /**
79
     * Check response status
80
     *
81
     * @throws ApigilityClient\Exception\RuntimeException
82
     * @return Bool
83
     */
84
    private function checkResponseStatus()
85
    {
86
        if (! $this->httpResponse->isSuccess()) {
87
            return new TriggerException($this->httpClient, $this->httpResponse);
88
        }
89
90
        return true;
91
    }
92
}
93