Issues in HttpHandlerResponseAbstract.php (master) - Issues in master - juniorb2ss/deathbycaptcha-php-sdk - Measure and Improve Code Quality continuously with Scrutinizer

Issues (30)

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/Abstracts/HttpHandlerResponseAbstract.php (8 issues)

Labels

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

<?php

namespace juniorb2ss\DeathByCaptcha\Abstracts;

use Psr\Http\Message\ResponseInterface;
use juniorb2ss\DeathByCaptcha\Exceptions\AccessDeniedException;
use juniorb2ss\DeathByCaptcha\Exceptions\CaptchaNotFoundException;
use juniorb2ss\DeathByCaptcha\Exceptions\InternalServiceException;
use juniorb2ss\DeathByCaptcha\Exceptions\InvalidCaptchaException;
use juniorb2ss\DeathByCaptcha\Exceptions\InvalidServiceResponseException;
use juniorb2ss\DeathByCaptcha\Exceptions\ServiceOverloadException;

abstract class HttpHandlerResponseAbstract
{

    /**
     * Define o content que deverá ser a resposta
     * do serviço
     * @var string
     */
    protected $contentTypeOk = 'application/json; charset=utf8';

    /**
     * Executa verificação da integridade da resposta
     * desde do cabeçalho do response até o conteúdo
     * @return void|ClientException
     */
    protected function handlerHttpResponseIsOk()
    {
        $response = $this->response;
class MyClass { }

$x = new MyClass();
$x->foo = true;
        $contentType = $response->getHeaderLine('Content-Type');

        $statusCode = $response->getStatusCode();

        // Efetua o tratamento do status code do response
        switch ($statusCode) {
            case 400:
                throw new InvalidCaptchaException;
                break;
function fx() {
    try {
        doSomething();
        return true;
    }
    catch (\Exception $e) {
        return false;
    }

    return false;
}
            case 403:
                throw new AccessDeniedException;
                break;
function fx() {
    try {
        doSomething();
        return true;
    }
    catch (\Exception $e) {
        return false;
    }

    return false;
}
            case 404:
                throw new CaptchaNotFoundException;
                break;
function fx() {
    try {
        doSomething();
        return true;
    }
    catch (\Exception $e) {
        return false;
    }

    return false;
}
            case 413:
                throw new InvalidCaptchaException;
                break;
function fx() {
    try {
        doSomething();
        return true;
    }
    catch (\Exception $e) {
        return false;
    }

    return false;
}
            case 500:
                throw new InternalServiceException;
            case 501:
                throw new InvalidCaptchaException;
                break;
function fx() {
    try {
        doSomething();
        return true;
    }
    catch (\Exception $e) {
        return false;
    }

    return false;
}
            case 503:
                throw new ServiceOverloadException;
                break;
function fx() {
    try {
        doSomething();
        return true;
    }
    catch (\Exception $e) {
        return false;
    }

    return false;
}
        }

        // Uma coisa básica é verificar o tipo do conteúdo
        // da resposta HTTP.
        // Parece a principio algo meio "desnecessário"
        // já que se a resposta for ok e for passado o
        // accept de json, técnicamente deverá retornar
        // o content type como json
        // mas... nunca se sabe, né?
        if (($contentType !== $this->contentTypeOk) or (empty((string)$response->getBody()))) {
// Logical operators have lower precedence:
$f = false or true;

// is executed like this:
($f = false) or true;


// Boolean operators have higher precedence:
$f = false || true;

// is executed like this:
$f = (false || true);
            throw new InvalidServiceResponseException;
        }
    }
}


GitHub Access Token became invalid

Issues (30)

Security Analysis no request data

src/Abstracts/HttpHandlerResponseAbstract.php (8 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Logical Operators are used for Control-Flow

juniorb2ss / deathbycaptcha-php-sdk

GitHub Access Token became invalid

Issues (30)

Security Analysis no request data

src/Abstracts/HttpHandlerResponseAbstract.php (8 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Logical Operators are used for Control-Flow

Duplication Side-by-Side

Filter issues like