Issues in AbstractResource.php (master) - Issues in master - Speicher210/kontakt.io-api - Measure and Improve Code Quality continuously with Scrutinizer

Issues (7)

Security Analysis no request data

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/AbstractResource.php (1 issue)

Labels

Bug 1

Severity

Minor 1

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

<?php

declare(strict_types = 1);

namespace Speicher210\KontaktIO;

use GuzzleHttp\Exception\ClientException;
use JMS\Serializer\SerializerBuilder;
use JMS\Serializer\SerializerInterface;
use Speicher210\KontaktIO\Exception\ApiException;
use Speicher210\KontaktIO\Exception\ApiKeyInvalidException;
use Speicher210\KontaktIO\Model\ApiErrorResponse;

/**
 * Abstract resource.
 */
class AbstractResource
{
    /**
     * The API client.
     *
     * @var Client
     */
    protected $client;

    /**
     * Serializer interface to serialize / deserialize the request / responses.
     *
     * @var SerializerInterface
     */
    protected $serializer;

    /**
     * Constructor.
     *
     * @param Client $client The API client.
     * @param SerializerInterface $serializer Serializer interface to serialize / deserialize the request / responses.
     */
    public function __construct(Client $client, SerializerInterface $serializer = null)
    {
        $this->client = $client;
        $this->serializer = $serializer ?? $this->buildSerializer();
    }

    private function buildSerializer(): SerializerInterface
    {
        return SerializerBuilder::create()->build();
    }

    /**
     * Create an ApiException from a client exception.
     *
     * @param ClientException $e The client exception.
     * @return ApiException
     * @throws \Speicher210\KontaktIO\Exception\ApiKeyInvalidException
     */
    protected function createApiException(ClientException $e): ApiException
    {
        $response = $e->getResponse();

        if (\in_array($response->getStatusCode(), [401, 403], true)) {
            throw ApiKeyInvalidException::forResponse($response);
/** @return stdClass|null */
function mayReturnNull() { }

function doesNotAcceptNull(stdClass $x) { }

// With potential error.
function withoutCheck() {
    $x = mayReturnNull();
    doesNotAcceptNull($x); // Potential error here.
}

// Safe - Alternative 1
function withCheck1() {
    $x = mayReturnNull();
    if ( ! $x instanceof stdClass) {
        throw new \LogicException('$x must be defined.');
    }
    doesNotAcceptNull($x);
}

// Safe - Alternative 2
function withCheck2() {
    $x = mayReturnNull();
    if ($x instanceof stdClass) {
        doesNotAcceptNull($x);
    }
}
        }

        if ($response->getBody()->getSize() > 0) {
            /** @var ApiErrorResponse $apiErrorResponse */
            $apiErrorResponse = $this->serializer->deserialize(
                $e->getResponse()->getBody(),
                ApiErrorResponse::class,
                'json'
            );
        } else {
            $apiErrorResponse = new ApiErrorResponse();
            $apiErrorResponse->setStatus($response->getStatusCode());
            $apiErrorResponse->setMessage($response->getReasonPhrase());
        }

        return new ApiException($apiErrorResponse, $e);
    }
}


1			<?php
2
3			declare(strict_types = 1);
4
5			namespace Speicher210\KontaktIO;
6
7			use GuzzleHttp\Exception\ClientException;
8			use JMS\Serializer\SerializerBuilder;
9			use JMS\Serializer\SerializerInterface;
10			use Speicher210\KontaktIO\Exception\ApiException;
11			use Speicher210\KontaktIO\Exception\ApiKeyInvalidException;
12			use Speicher210\KontaktIO\Model\ApiErrorResponse;
13
14			/**
15			* Abstract resource.
16			*/
17			class AbstractResource
18			{
19			/**
20			* The API client.
21			*
22			* @var Client
23			*/
24			protected $client;
25
26			/**
27			* Serializer interface to serialize / deserialize the request / responses.
28			*
29			* @var SerializerInterface
30			*/
31			protected $serializer;
32
33			/**
34			* Constructor.
35			*
36			* @param Client $client The API client.
37			* @param SerializerInterface $serializer Serializer interface to serialize / deserialize the request / responses.
38			*/
39			public function __construct(Client $client, SerializerInterface $serializer = null)
40			{
41			$this->client = $client;
42			$this->serializer = $serializer ?? $this->buildSerializer();
43			}
44
45			private function buildSerializer(): SerializerInterface
46			{
47			return SerializerBuilder::create()->build();
48			}
49
50			/**
51			* Create an ApiException from a client exception.
52			*
53			* @param ClientException $e The client exception.
54			* @return ApiException
55			* @throws \Speicher210\KontaktIO\Exception\ApiKeyInvalidException
56			*/
57			protected function createApiException(ClientException $e): ApiException
58			{
59			$response = $e->getResponse();
60
61			if (\in_array($response->getStatusCode(), [401, 403], true)) {
62			throw ApiKeyInvalidException::forResponse($response);
			0 ignored issues – show Bug introduced 2017-02-23 12:43 UTC by Report Bug Copy Issue Report Show Similar Issues like this It seems like `$response` defined by `$e->getResponse()` on line `59` can be `null`; however, `Speicher210\KontaktIO\Ex...xception::forResponse()` does not accept `null`, maybe add an additional type check? Unless you are absolutely sure that the expression can never be null because of other conditions, we strongly recommend to add an additional type check to your code: /** @return stdClass\|null */ function mayReturnNull() { } function doesNotAcceptNull(stdClass $x) { } // With potential error. function withoutCheck() { $x = mayReturnNull(); doesNotAcceptNull($x); // Potential error here. } // Safe - Alternative 1 function withCheck1() { $x = mayReturnNull(); if ( ! $x instanceof stdClass) { throw new \LogicException('$x must be defined.'); } doesNotAcceptNull($x); } // Safe - Alternative 2 function withCheck2() { $x = mayReturnNull(); if ($x instanceof stdClass) { doesNotAcceptNull($x); } } Loading history...
63			}
64
65			if ($response->getBody()->getSize() > 0) {
66			/** @var ApiErrorResponse $apiErrorResponse */
67			$apiErrorResponse = $this->serializer->deserialize(
68			$e->getResponse()->getBody(),
69			ApiErrorResponse::class,
70			'json'
71			);
72			} else {
73			$apiErrorResponse = new ApiErrorResponse();
74			$apiErrorResponse->setStatus($response->getStatusCode());
75			$apiErrorResponse->setMessage($response->getReasonPhrase());
76			}
77
78			return new ApiException($apiErrorResponse, $e);
79			}
80			}
81

GitHub Access Token became invalid

Issues (7)

Security Analysis no request data

src/AbstractResource.php (1 issue)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Speicher210 / kontakt.io-api

GitHub Access Token became invalid

Issues (7)

Security Analysis no request data

src/AbstractResource.php (1 issue)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like