Issues in SmsHandlerInterface.php (master) - Issues in master - apiaryhq/silex-sms-login-provider - Measure and Improve Code Quality continuously with Scrutinizer

Issues (15)

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

Labels

Coding Style 1

Severity

Informational 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
/**
 * This file is part of the Apiary SMS Login Provider package.
 *
 * (c) Darren Mothersele <[email protected]>
 *
 * For the full copyright and license information, please view the LICENSE
 * file that was distributed with this source code.
 */

namespace Apiary\SmsLoginProvider\SmsHandler;

/**
 * Interface SmsHandlerInterface
 * @package Apiary
 */
interface SmsHandlerInterface
{


    /**
     * Set the default From address or number
     * @param string $from
     */
    public function setDefaultFrom($from);

    /**
     * Lookup, validate a number and convert to E.164
     * @param string $number Phone number in any format
     * @param string $countryCode ISO Country code
     * @return string Validated number in E.164 format
     * @throws Apiary\SmsLoginProvider\Exception\InvalidPhoneNumberException
     */
    public function lookupNumber($number, $countryCode);


    /**
     * Send a single SMS message
     * @param $from
     * @param $to
     * @param $body
     * @return string identifier of sent message
     * @throws Apiary\SmsLoginProvider\Exception\SMSSendFailException
     */
    public function sendSMS($to, $body, $from = null);

}
// Incorrect placement according to PSR2
class MyClass
{
    public function foo()
    {

    }
    // This blank line is not allowed.

}

// Correct
class MyClass
{
    public function foo()
    {

    } // No blank lines after this line.
}

1			<?php
2			/**
3			* This file is part of the Apiary SMS Login Provider package.
4			*
5			* (c) Darren Mothersele <[email protected]>
6			*
7			* For the full copyright and license information, please view the LICENSE
8			* file that was distributed with this source code.
9			*/
10
11			namespace Apiary\SmsLoginProvider\SmsHandler;
12
13			/**
14			* Interface SmsHandlerInterface
15			* @package Apiary
16			*/
17			interface SmsHandlerInterface
18			{
19
20
21			/**
22			* Set the default From address or number
23			* @param string $from
24			*/
25			public function setDefaultFrom($from);
26
27			/**
28			* Lookup, validate a number and convert to E.164
29			* @param string $number Phone number in any format
30			* @param string $countryCode ISO Country code
31			* @return string Validated number in E.164 format
32			* @throws Apiary\SmsLoginProvider\Exception\InvalidPhoneNumberException
33			*/
34			public function lookupNumber($number, $countryCode);
35
36
37			/**
38			* Send a single SMS message
39			* @param $from
40			* @param $to
41			* @param $body
42			* @return string identifier of sent message
43			* @throws Apiary\SmsLoginProvider\Exception\SMSSendFailException
44			*/
45			public function sendSMS($to, $body, $from = null);
46
47			}
			0 ignored issues – show Coding Style introduced 2015-11-22 02:43 UTC by Report Bug Copy Issue Report Show Similar Issues like this According to PSR2, the closing brace of interfaces should be placed on the next line directly after the body. Below you find some examples: // Incorrect placement according to PSR2 class MyClass { public function foo() { } // This blank line is not allowed. } // Correct class MyClass { public function foo() { } // No blank lines after this line. } Loading history...

apiaryhq / silex-sms-login-provider

Issues (15)

Security Analysis no request data

src/SmsHandler/SmsHandlerInterface.php (1 issue)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like