Issues in Registration.php (master) - Issues in master - teresko/palladium - Measure and Improve Code Quality continuously with Scrutinizer

Issues (12)

Security Analysis no request data

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.

Regex Injection

Regex Injection enables an attacker to execute arbitrary code in your PHP process.

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.

Response Splitting

Response Splitting can be used to send arbitrary responses.

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.

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.

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.

Code Injection

Code Injection enables an attacker to execute arbitrary code on the server.

Variable Injection

Variable Injection enables an attacker to overwrite program variables with custom data, and can lead to further vulnerabilities.

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.

Other Vulnerability

This category comprises other attack vectors such as manipulating the PHP runtime, loading custom extensions, freezing the runtime, or similar.

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.

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.

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.

Header Injection

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/Palladium/Service/Registration.php (2 issues)

Labels

Bug 2

Severity

<?php

namespace Palladium\Service;

/**
 * Code for creating new identities
 */

use Palladium\Entity as Entity;
use Palladium\Component\DataMapper;
use Palladium\Exception\IdentityConflict;
use Palladium\Repository\Identity as Repository;
use Psr\Log\LoggerInterface;

class Registration
{

    const DEFAULT_TOKEN_LIFESPAN = 28800; // 8 hours
    const DEFAULT_NONCE_LIFESPAN = 7200; // 2 hours
    const DEFAULT_HASH_COST = 12;

    private $repository;
    private $accountMapper;
    private $logger;
    private $hashCost;

    /**
     * @param Repository $repository Repository for abstracting persistence layer structures
     * @param LoggerInterface $logger PSR-3 compatible logger
     * @param int $hashCost Optional value for setting the cost of hashing algorythm (default: 12)
     */
    public function __construct(Repository $repository, DataMapper $accountMapper, LoggerInterface $logger, $hashCost = Registration::DEFAULT_HASH_COST)
    {
        $this->repository = $repository;
        $this->accountMapper = $accountMapper;
        $this->logger = $logger;
        $this->hashCost = $hashCost;
    }


    /**
     * @throws IdentityConflict if attempting to register a new identity, with the same identifier
     */
    public function createStandardIdentity(string $identifier, string $password, int $tokenLifespan = Registration::DEFAULT_TOKEN_LIFESPAN): Entity\StandardIdentity
    {
        $identity = new Entity\StandardIdentity;

        $identity->setIdentifier($identifier);
        $identity->setPassword($password, $this->hashCost);
        $identity->setTokenEndOfLife(time() + $tokenLifespan);

        $this->prepareNewIdentity($identity);

        if ($this->repository->has($identity)) {
            $this->logger->notice('identifier already registered', [
                'input' => [
                    'identifier' => $identifier,
                ],
            ]);

            throw new IdentityConflict;
        }

        $this->repository->save($identity);

        return $identity;
    }


    public function createNonceIdentity($accountId, $identityLifespan = Registration::DEFAULT_NONCE_LIFESPAN): Entity\NonceIdentity
    {
        $identity = new Entity\NonceIdentity;

        $identity->setAccountId($accountId);
        $identity->setExpiresOn(time() + $identityLifespan);
        $identity->setStatus(Entity\Identity::STATUS_ACTIVE);
        $identity->generateNewNonce();
        $identity->generateNewKey($this->hashCost);

        $this->repository->save($identity);

        $this->logger->info('new single-use identity created', [
            'user' => [
                'account' => $identity->getAccountId(),
                'identity' => $identity->getId(),
            ],
        ]);

        return $identity;
    }


    private function prepareNewIdentity(Entity\StandardIdentity $identity)
    {
        $identity->setStatus(Entity\Identity::STATUS_NEW);
        $identity->generateToken();
        $identity->setTokenAction(Entity\Identity::ACTION_VERIFY);
    }


    public function bindAccountToIdentity(int $accountId, Entity\Identity $identity)
    {
        $identity->setAccountId($accountId);
        $this->accountMapper->store($identity);
                              store($identity);

        $this->logger->info('new identifier registered', [
            'user' => [
                'account' => $identity->getAccountId(),
                'identity' => $identity->getId(),
            ],
        ]);
    }


    public function verifyStandardIdentity(Entity\StandardIdentity $identity)
    {
        $identity->setStatus(Entity\Identity::STATUS_ACTIVE);
        $identity->clearToken();

        $this->repository->save($identity);

        $this->logger->info('identity verified', [
            'input' => [
                'token' => $identity->getToken(),
class A
{
    function getObject()
    {
        return null;
    }

}

$a = new A();
if ($a->getObject()) {
            ],
            'user' => [
                'account' => $identity->getAccountId(),
                'identity' => $identity->getId(),
            ],
        ]);
    }
}


teresko / palladium

Issues (12)

Security Analysis no request data

src/Palladium/Service/Registration.php (2 issues)

Labels

Severity

Introduced By

Duplication Side-by-Side

Filter issues like