Issues in Moip.php (master) - Issues in master - artesaos/moip - Measure and Improve Code Quality continuously with Scrutinizer

Issues (4)

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/Moip.php (2 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 Artesaos\Moip;

use Moip\Moip as Api;

/**
 * Class Moip.
 *
 * @package Artesaos\Moip
 */
class Moip
{
    /**
     * Class Moip sdk.
     *
     * @var \Moip\Moip
     **/
    private $moip;

    /**
     * Moip constructor.
     *
     * @param \Moip\Moip $api
     */
    function __construct(Api $api)

    {
        $this->moip = $api;

        return $this;

    }

    /**
     * Return a intance of package.
     *
     * @return \Moip\Moip
     */
    public function getApi()
    {
        return $this->moip;
    }

    /**
     * Start Moip sdk.
     *
     * @deprecated
     */
    public function start()
    {
        return $this;
    }

    /**
     * Create a new Accounts instance.
     *
     * @return \Moip\Resource\Account
     */
    public function accounts()
    {
        return $this->moip->accounts();
    }

    /**
     * Create a new Customer instance.
     *
     * @return \Moip\Resource\Customer
     */
    public function customers()
    {
        return $this->moip->customers();
    }

    /**
     * Create a new Entry instance.
     *
     * @return \Moip\Resource\Entry
     */
    public function entries()
    {
        return $this->moip->entries();
    }

    /**
     * Create a new Order instance.
     *
     * @return \Moip\Resource\Orders
     */
    public function orders()
    {
        return $this->moip->orders();
    }

    /**
     * Create a new Payment instance.
     *
     * @return \Moip\Resource\Payment
     */
    public function payments()
    {
        return $this->moip->payments();
    }

    /**
     * Create a new Multiorders instance.
     *
     * @return \Moip\Resource\Multiorders
     */
    public function multiorders()
    {
        return $this->moip->multiorders();
    }

    /**
     * Create a new Notifications instance.
     *
     * @return \Moip\Resource\NotificationPreferences
     */
    public function notifications()
    {
        return $this->moip->notifications();
    }

    /**
     * Create a new Tranfers instance.
     *
     * @return \Moip\Resource\Transfers
     */
    public function transfers()
    {
        return $this->moip->transfers();
    }

    /**
     * Create a new Holder instance.
     *
     * @return \Moip\Resource\Holder
     */
    public function holders()
    {
        return $this->moip->holders();
    }
}


1			<?php
2
3			namespace Artesaos\Moip;
4
5			use Moip\Moip as Api;
6
7			/**
8			* Class Moip.
9			*
10			* @package Artesaos\Moip
11			*/
12			class Moip
13			{
14			/**
15			* Class Moip sdk.
16			*
17			* @var \Moip\Moip
18			**/
19			private $moip;
20
21			/**
22			* Moip constructor.
23			*
24			* @param \Moip\Moip $api
25			*/
26			function __construct(Api $api)
			0 ignored issues – show Best Practice introduced 2017-04-03 23:08 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...
27			{
28			$this->moip = $api;
29
30			return $this;
			0 ignored issues – show Bug introduced 2017-04-03 23:08 UTC by Report Bug Copy Issue Report Show Similar Issues like this Constructors do not have meaningful return values, anything that is returned from here is discarded. Are you sure this is correct? Loading history...
31			}
32
33			/**
34			* Return a intance of package.
35			*
36			* @return \Moip\Moip
37			*/
38			public function getApi()
39			{
40			return $this->moip;
41			}
42
43			/**
44			* Start Moip sdk.
45			*
46			* @deprecated
47			*/
48			public function start()
49			{
50			return $this;
51			}
52
53			/**
54			* Create a new Accounts instance.
55			*
56			* @return \Moip\Resource\Account
57			*/
58			public function accounts()
59			{
60			return $this->moip->accounts();
61			}
62
63			/**
64			* Create a new Customer instance.
65			*
66			* @return \Moip\Resource\Customer
67			*/
68			public function customers()
69			{
70			return $this->moip->customers();
71			}
72
73			/**
74			* Create a new Entry instance.
75			*
76			* @return \Moip\Resource\Entry
77			*/
78			public function entries()
79			{
80			return $this->moip->entries();
81			}
82
83			/**
84			* Create a new Order instance.
85			*
86			* @return \Moip\Resource\Orders
87			*/
88			public function orders()
89			{
90			return $this->moip->orders();
91			}
92
93			/**
94			* Create a new Payment instance.
95			*
96			* @return \Moip\Resource\Payment
97			*/
98			public function payments()
99			{
100			return $this->moip->payments();
101			}
102
103			/**
104			* Create a new Multiorders instance.
105			*
106			* @return \Moip\Resource\Multiorders
107			*/
108			public function multiorders()
109			{
110			return $this->moip->multiorders();
111			}
112
113			/**
114			* Create a new Notifications instance.
115			*
116			* @return \Moip\Resource\NotificationPreferences
117			*/
118			public function notifications()
119			{
120			return $this->moip->notifications();
121			}
122
123			/**
124			* Create a new Tranfers instance.
125			*
126			* @return \Moip\Resource\Transfers
127			*/
128			public function transfers()
129			{
130			return $this->moip->transfers();
131			}
132
133			/**
134			* Create a new Holder instance.
135			*
136			* @return \Moip\Resource\Holder
137			*/
138			public function holders()
139			{
140			return $this->moip->holders();
141			}
142			}
143

artesaos / moip

Issues (4)

Security Analysis no request data

src/Moip.php (2 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like