Issues in DMSCartBackendInterface.php (master) - Issues in master - silverstripe/silverstripe-dms-cart - Measure and Improve Code Quality continuously with Scrutinizer

Issues (199)

Security Analysis not enabled

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.

code/interfaces/DMSCartBackendInterface.php (1 issue)

Labels

Severity

Minor 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

/**
 * Interface DMSCartBackendInterface represents the contract for a Session Backend
 */
interface DMSCartBackendInterface
namespace YourVendor;

class YourClass { }
{
    /**
     * Get all the {@link DMSRequestItem} objects
     * serialized in the cart.
     *
     * @return array
     */
    public function getItems();

    /**
     * Returns a single element from the items list
     *
     * @param int $id
     *
     * @return DMSRequestItem|boolean
     */
    public function getItem($id);

    /**
     * Add an {@link DMSRequestItem} object into the cart.
     *
     * @param DMSRequestItem $item
     *
     * @return DMSCartBackendInterface
     */
    public function addItem(DMSRequestItem $item);

    /**
     * Remove a {@link DMSRequestItem} object from the cart.
     *
     * @param DMSRequestItem $item
     *
     * @return DMSCartBackendInterface
     */
    public function removeItem(DMSRequestItem $item);

    /**
     * Removes a {@link DMSRequestItem} from the cart by it's id
     *
     * @param int $itemID
     *
     * @return DMSCartBackendInterface
     *
     */
    public function removeItemByID($itemID);

    /**
     * Flushes the cart
     *
     * @return DMSCartBackendInterface
     */
    public function emptyCart();

    /**
     * Set the backURL to be a Session variable for the current Document Cart
     *
     * @param string $backURL
     *
     * @return DMSCartBackendInterface
     */
    public function setBackUrl($backURL);

    /**
     * Returns the backURL for the current Document Cart
     *
     * @return string
     */
    public function getBackUrl();

    /**
     * Sets the recipients information
     *
     * @param array $receiverInfo
     *
     * @return DMSCartBackendInterface
     */
    public function setReceiverInfo(array $receiverInfo = array());

    /**
     * Retrieves the recipients info
     *
     * @return array
     */
    public function getReceiverInfo();
}


1			<?php
2
3			/**
4			* Interface DMSCartBackendInterface represents the contract for a Session Backend
5			*/
6			interface DMSCartBackendInterface
			0 ignored issues – show Coding Style Compatibility introduced 2017-05-23 04:54 UTC by Report Bug Copy Issue Report Show Similar Issues like this Each interface must be in a namespace of at least one level (a top-level vendor name) You can fix this by adding a namespace to your class: namespace YourVendor; class YourClass { } When choosing a vendor namespace, try to pick something that is not too generic to avoid conflicts with other libraries. Loading history...
7			{
8			/**
9			* Get all the {@link DMSRequestItem} objects
10			* serialized in the cart.
11			*
12			* @return array
13			*/
14			public function getItems();
15
16			/**
17			* Returns a single element from the items list
18			*
19			* @param int $id
20			*
21			* @return DMSRequestItem\|boolean
22			*/
23			public function getItem($id);
24
25			/**
26			* Add an {@link DMSRequestItem} object into the cart.
27			*
28			* @param DMSRequestItem $item
29			*
30			* @return DMSCartBackendInterface
31			*/
32			public function addItem(DMSRequestItem $item);
33
34			/**
35			* Remove a {@link DMSRequestItem} object from the cart.
36			*
37			* @param DMSRequestItem $item
38			*
39			* @return DMSCartBackendInterface
40			*/
41			public function removeItem(DMSRequestItem $item);
42
43			/**
44			* Removes a {@link DMSRequestItem} from the cart by it's id
45			*
46			* @param int $itemID
47			*
48			* @return DMSCartBackendInterface
49			*
50			*/
51			public function removeItemByID($itemID);
52
53			/**
54			* Flushes the cart
55			*
56			* @return DMSCartBackendInterface
57			*/
58			public function emptyCart();
59
60			/**
61			* Set the backURL to be a Session variable for the current Document Cart
62			*
63			* @param string $backURL
64			*
65			* @return DMSCartBackendInterface
66			*/
67			public function setBackUrl($backURL);
68
69			/**
70			* Returns the backURL for the current Document Cart
71			*
72			* @return string
73			*/
74			public function getBackUrl();
75
76			/**
77			* Sets the recipients information
78			*
79			* @param array $receiverInfo
80			*
81			* @return DMSCartBackendInterface
82			*/
83			public function setReceiverInfo(array $receiverInfo = array());
84
85			/**
86			* Retrieves the recipients info
87			*
88			* @return array
89			*/
90			public function getReceiverInfo();
91			}
92

silverstripe / silverstripe-dms-cart

Issues (199)

Security Analysis not enabled

code/interfaces/DMSCartBackendInterface.php (1 issue)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like