Issues in TimeZone.php (master) - Issues in master - Code-Mine-Development/valueobjects - Measure and Improve Code Quality continuously with Scrutinizer

Issues (158)

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/DateTime/TimeZone.php (4 issues)

Labels

Severity

Minor 4

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 ValueObjects\DateTime;

use ValueObjects\DateTime\Exception\InvalidTimeZoneException;
use ValueObjects\StringLiteral\StringLiteral;
use ValueObjects\Util\Util;
use ValueObjects\ValueObjectInterface;

class TimeZone implements ValueObjectInterface
{
    /** @var StringLiteral */
    protected $name;

    /**
     * Returns a new Time object from native timezone name
     *
     * @param  string $name
/**
 * @param array $germany
 * @param array $island
 * @param array $italy
 */
function finale($germany, $island) {
    return "2:1";
}
     *
     * @return self
     */
    public static function fromNative()
    {
        $args = func_get_args();

        $name = new StringLiteral($args[0]);

        return new static($name);
    }

    /**
     * Returns a new Time from a native PHP \DateTime
     *
     * @param  \DateTimeZone $timezone
     *
     * @return self
     */
    public static function fromNativeDateTimeZone(\DateTimeZone $timezone)
    {
        return static::fromNative($timezone->getName());
    }

    /**
     * Returns default TimeZone
     *
     * @return self
     */
    public static function fromDefault()
    {
        return new static(new StringLiteral(date_default_timezone_get()));
    }

    /**
     * Returns a new TimeZone object
     *
     * @param StringLiteral $name
     *
     * @throws InvalidTimeZoneException
     */
    public function __construct(StringLiteral $name)
    {
        $availableTimezones   = timezone_identifiers_list();
        $availableTimezones[] = 'Z';

        if (!in_array($name->toNative(), $availableTimezones)
            && !preg_match('/[+-]\d{2}:?\d{2}/', $name->toNative())
        ) {
            throw new InvalidTimeZoneException($name);
        }

        $this->name = $name;
    }

    /**
     * Returns a native PHP \DateTimeZone version of the current TimeZone.
     *
     * @return \DateTimeZone
     */
    public function toNativeDateTimeZone()
    {
        return new \DateTimeZone($this->getName()->toNative());
    }

    /**
     * Tells whether two DateTimeZone are equal by comparing their names
     *
     * @param  ValueObjectInterface $timezone
     *
     * @return bool
     */
    public function sameValueAs(ValueObjectInterface $timezone)
    {
        if (FALSE === Util::classEquals($this, $timezone)) {
            return FALSE;
        }

        return $this->getName()->sameValueAs($timezone->getName());
interface User
{
    /** @return string */
    public function getPassword();
}

class MyUser implements User
{
    public function getPassword()
    {
        // return something
    }

    public function getDisplayName()
    {
        // return some name.
    }
}

class AuthSystem
{
    public function authenticate(User $user)
    {
        $this->logger->info(sprintf('Authenticating %s.', $user->getDisplayName()));
        // do something.
    }
}
    }

    /**
     * Returns timezone name
     *
     * @return StringLiteral
     */
    public function getName()
    {
        return clone $this->name;
    }

    /**
     * Returns timezone name as string
     *
     * @return string
     */
    public function __toString()
    {
        return $this->getName()->__toString();
    }

    function jsonSerialize()

    {
        return (string)$this;
    }


}


1		<?php
2
3		namespace ValueObjects\DateTime;
4
5		use ValueObjects\DateTime\Exception\InvalidTimeZoneException;
6		use ValueObjects\StringLiteral\StringLiteral;
7		use ValueObjects\Util\Util;
8		use ValueObjects\ValueObjectInterface;
9
10		class TimeZone implements ValueObjectInterface
11		{
12		/** @var StringLiteral */
13		protected $name;
14
15		/**
16		* Returns a new Time object from native timezone name
17		*
18		* @param string $name
		0 ignored issues – show Bug introduced 2016-04-25 08:47 UTC by Report Bug Copy Issue Report Show Similar Issues like this There is no parameter named `$name`. Was it maybe removed? This check looks for PHPDoc comments describing methods or function parameters that do not exist on the corresponding method or function. Consider the following example. The parameter `$italy` is not defined by the method `finale(...)`. /** * @param array $germany * @param array $island * @param array $italy */ function finale($germany, $island) { return "2:1"; } The most likely cause is that the parameter was removed, but the annotation was not. Loading history...
19		*
20		* @return self
21		*/
22	4	public static function fromNative()
23		{
24	4	$args = func_get_args();
25
26	4	$name = new StringLiteral($args[0]);
27
28	4	return new static($name);
29		}
30
31		/**
32		* Returns a new Time from a native PHP \DateTime
33		*
34		* @param \DateTimeZone $timezone
35		*
36		* @return self
37		*/
38	2	public static function fromNativeDateTimeZone(\DateTimeZone $timezone)
39		{
40	2	return static::fromNative($timezone->getName());
41		}
42
43		/**
44		* Returns default TimeZone
45		*
46		* @return self
47		*/
48	2	public static function fromDefault()
49		{
50	2	return new static(new StringLiteral(date_default_timezone_get()));
51		}
52
53		/**
54		* Returns a new TimeZone object
55		*
56		* @param StringLiteral $name
57		*
58		* @throws InvalidTimeZoneException
59		*/
60	17	public function __construct(StringLiteral $name)
61		{
62	17	$availableTimezones = timezone_identifiers_list();
63	17	$availableTimezones[] = 'Z';
64
65	17	if (!in_array($name->toNative(), $availableTimezones)
66	17	&& !preg_match('/[+-]\d{2}:?\d{2}/', $name->toNative())
67	17	) {
68	1	throw new InvalidTimeZoneException($name);
69		}
70
71	16	$this->name = $name;
72	16	}
73
74		/**
75		* Returns a native PHP \DateTimeZone version of the current TimeZone.
76		*
77		* @return \DateTimeZone
78		*/
79	3	public function toNativeDateTimeZone()
80		{
81	3	return new \DateTimeZone($this->getName()->toNative());
82		}
83
84		/**
85		* Tells whether two DateTimeZone are equal by comparing their names
86		*
87		* @param ValueObjectInterface $timezone
88		*
89		* @return bool
90		*/
91	7	public function sameValueAs(ValueObjectInterface $timezone)
92		{
93	7	if (FALSE === Util::classEquals($this, $timezone)) {
94	1	return FALSE;
95		}
96
97	7	return $this->getName()->sameValueAs($timezone->getName());
		0 ignored issues – show Bug introduced 2016-04-25 08:47 UTC by Report Bug Copy Issue Report Show Similar Issues like this It seems like you code against a concrete implementation and not the interface `ValueObjects\ValueObjectInterface` as the method `getName()` does only exist in the following implementations of said interface: `ValueObjects\DateTime\Month`, `ValueObjects\DateTime\TimeZone`, `ValueObjects\DateTime\WeekDay`, `ValueObjects\Enum\Enum`, `ValueObjects\Geography\Address`, `ValueObjects\Geography\Continent`, `ValueObjects\Geography\Country`, `ValueObjects\Geography\CountryCode`, `ValueObjects\Geography\DistanceFormula`, `ValueObjects\Geography\DistanceUnit`, `ValueObjects\Geography\Ellipsoid`, `ValueObjects\Geography\Street`, `ValueObjects\Money\CurrencyCode`, `ValueObjects\Number\RoundingMode`, `ValueObjects\Person\Gender`, `ValueObjects\Web\IPAddressVersion`. Let’s take a look at an example: interface User { /** @return string / public function getPassword(); } class MyUser implements User { public function getPassword() { // return something } public function getDisplayName() { // return some name. } } class AuthSystem { public function authenticate(User $user) { $this->logger->info(sprintf('Authenticating %s.', $user->getDisplayName())); // do something. } } In the above example, the authenticate() method works fine as long as you just pass instances of MyUser. However, if you now also want to pass a different implementation of User which does not have a getDisplayName() method, the code will break. Available Fixes Change the type-hint for the parameter: class AuthSystem { public function authenticate(MyUser $user) { / ... / } } Add an additional type-check: class AuthSystem { public function authenticate(User $user) { if ($user instanceof MyUser) { $this->logger->info(/* ... /); } // or alternatively if ( ! $user instanceof MyUser) { throw new \LogicException( '$user must be an instance of MyUser, ' .'other instances are not supported.' ); } } } Note:* PHP Analyzer uses reverse abstract interpretation to narrow down the types inside the if block in such a case. Add the method to the interface: interface User { /** @return string / public function getPassword(); /* @return string */ public function getDisplayName(); } Loading history...
98		}
99
100		/**
101		* Returns timezone name
102		*
103		* @return StringLiteral
104		*/
105	15	public function getName()
106		{
107	15	return clone $this->name;
108		}
109
110		/**
111		* Returns timezone name as string
112		*
113		* @return string
114		*/
115	4	public function __toString()
116		{
117	4	return $this->getName()->__toString();
118		}
119
120		function jsonSerialize()
		0 ignored issues – show Best Practice introduced 2016-04-25 08:47 UTC by Report Bug Copy Issue Report Show Similar Issues like this It is generally recommended to explicitly declare the visibility for methods. Adding explicit visibility (`private`, `protected`, or `public`) is generally recommend to communicate to other developers how, and from where this method is intended to be used. Loading history... Comprehensibility Best Practice introduced 2016-04-25 08:47 UTC by Report Bug Copy Issue Report Show Similar Issues like this It is recommend to declare an explicit visibility for `jsonSerialize`. Generally, we recommend to declare visibility for all methods in your source code. This has the advantage of clearly communication to other developers, and also yourself, how this method should be consumed. If you are not sure which visibility to choose, it is a good idea to start with the most restrictive visibility, and then raise visibility as needed, i.e. start with `private`, and only raise it to `protected` if a sub-class needs to have access, or `public` if an external class needs access. Loading history...
121		{
122		return (string)$this;
123		}
124
125
126		}
127

Code-Mine-Development / valueobjects

Issues (158)

Security Analysis no request data

src/DateTime/TimeZone.php (4 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Available Fixes

Duplication Side-by-Side

Filter issues like