Issues (547)

Security Analysis    not enabled

This project does not seem to handle request data directly as such no vulnerable execution paths were found.

  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.

Model/Methods/Klarna.php (6 issues)

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

1
<?php
2
3
/**
4
 * PAYONE Magento 2 Connector is free software: you can redistribute it and/or modify
5
 * it under the terms of the GNU Lesser General Public License as published by
6
 * the Free Software Foundation, either version 3 of the License, or
7
 * (at your option) any later version.
8
 *
9
 * PAYONE Magento 2 Connector is distributed in the hope that it will be useful,
10
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
11
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
12
 * GNU Lesser General Public License for more details.
13
 *
14
 * You should have received a copy of the GNU Lesser General Public License
15
 * along with PAYONE Magento 2 Connector. If not, see <http://www.gnu.org/licenses/>.
16
 *
17
 * PHP version 5
18
 *
19
 * @category  Payone
20
 * @package   Payone_Magento2_Plugin
21
 * @author    FATCHIP GmbH <[email protected]>
22
 * @copyright 2003 - 2016 Payone GmbH
23
 * @license   <http://www.gnu.org/licenses/> GNU Lesser General Public License
24
 * @link      http://www.payone.de
25
 */
26
27
namespace Payone\Core\Model\Methods;
28
29
use Payone\Core\Model\PayoneConfig;
30
use Magento\Sales\Model\Order;
31
use Magento\Framework\DataObject;
32
33
/**
34
 * Model for Klarna invoice payment method
35
 */
36
class Klarna extends PayoneMethod
37
{
38
    /**
39
     * Payment method code
40
     *
41
     * @var string
42
     */
43
    protected $_code = PayoneConfig::METHOD_KLARNA;
44
45
    /**
46
     * Info instructions block path
47
     *
48
     * @var string
49
     */
50
    protected $_infoBlockType = 'Payone\Core\Block\Info\SafeInvoice';
51
52
    /**
53
     * Clearingtype for PAYONE authorization request
54
     *
55
     * @var string
56
     */
57
    protected $sClearingtype = 'fnc';
58
59
    /**
60
     * Determines if the invoice information has to be added
61
     * to the authorization-request
62
     *
63
     * @var bool
64
     */
65
    protected $blNeedsProductInfo = true;
66
67
    /**
68
     * Keys that need to be assigned to the additionalinformation fields
69
     *
70
     * @var array
71
     */
72
    protected $aAssignKeys = [
73
        'telephone',
74
        'addinfo',
75
        'del_addinfo',
76
        'gender',
77
        'personal_id'
78
    ];
79
80
    /**
81
     * Map of value that can be directly added to the PAYONE request
82
     *
83
     * @var array
84
     */
85
    protected $aDirectAssignMap = [
86
        'telephone' => 'telephonenumber',
87
        'addinfo' => 'addressaddition',
88
        'del_addinfo' => 'shipping_addressaddition',
89
        'personal_id' => 'personalid',
90
        'dob' => 'birthday',
91
    ];
92
93
    /**
94
     * Return parameters specific to this payment type
95
     *
96
     * @param  Order $oOrder
97
     * @return array
98
     */
99
    public function getPaymentSpecificParameters(Order $oOrder)
100
    {
101
        $aParams = [
102
            'financingtype' => 'KLV',
103
        ];
104
105
        $oInfoInstance = $this->getInfoInstance();
106
        foreach ($this->aDirectAssignMap as $sFrom => $sTo) {
107
            $sValue = $oInfoInstance->getAdditionalInformation($sFrom);
108
            if ($sValue) {
109
                $aParams[$sTo] = $sValue;
110
            }
111
        }
112
113
        $sGender = $oInfoInstance->getAdditionalInformation('gender');
114
        if ($sGender) {
115
            $aParams['gender'] = $sGender;
116
            $aParams['salutation'] = $sGender == 'm' ? 'Herr' : 'Frau';
117
        }
118
119
        return $aParams;
120
    }
121
122
    /**
123
     * Returns formatted birthday if possible
124
     *
125
     * @param  DataObject $data
126
     * @return string|false
127
     */
128 View Code Duplication
    protected function getFormattedBirthday(DataObject $data)
0 ignored issues
show
This method seems to be duplicated in your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
129
    {
130
        $sFormattedDob = false;
131
132
        $sBirthday = $this->toolkitHelper->getAdditionalDataEntry($data, 'birthday');
133
        $sBirthmonth = $this->toolkitHelper->getAdditionalDataEntry($data, 'birthmonth');
134
        $sBirthyear = $this->toolkitHelper->getAdditionalDataEntry($data, 'birthyear');
135
        if ($sBirthday && $sBirthmonth && $sBirthyear) {
0 ignored issues
show
Bug Best Practice introduced by
The expression $sBirthday of type string|null is loosely compared to true; this is ambiguous if the string can be empty. You might want to explicitly use !== null instead.

In PHP, under loose comparison (like ==, or !=, or switch conditions), values of different types might be equal.

For string values, the empty string '' is a special case, in particular the following results might be unexpected:

''   == false // true
''   == null  // true
'ab' == false // false
'ab' == null  // false

// It is often better to use strict comparison
'' === false // false
'' === null  // false
Loading history...
Bug Best Practice introduced by
The expression $sBirthmonth of type string|null is loosely compared to true; this is ambiguous if the string can be empty. You might want to explicitly use !== null instead.

In PHP, under loose comparison (like ==, or !=, or switch conditions), values of different types might be equal.

For string values, the empty string '' is a special case, in particular the following results might be unexpected:

''   == false // true
''   == null  // true
'ab' == false // false
'ab' == null  // false

// It is often better to use strict comparison
'' === false // false
'' === null  // false
Loading history...
Bug Best Practice introduced by
The expression $sBirthyear of type string|null is loosely compared to true; this is ambiguous if the string can be empty. You might want to explicitly use !== null instead.

In PHP, under loose comparison (like ==, or !=, or switch conditions), values of different types might be equal.

For string values, the empty string '' is a special case, in particular the following results might be unexpected:

''   == false // true
''   == null  // true
'ab' == false // false
'ab' == null  // false

// It is often better to use strict comparison
'' === false // false
'' === null  // false
Loading history...
136
            $sDob = $sBirthyear.'-'.$sBirthmonth.'-'.$sBirthday;
137
            $iDobTime = strtotime($sDob);
138
            if ($iDobTime !== false) {
139
                $sFormattedDob = date('Ymd', $iDobTime);
140
            }
141
        }
142
        return $sFormattedDob;
143
    }
144
145
    /**
146
     * Add the checkout-form-data to the checkout session
147
     *
148
     * @param  DataObject $data
149
     * @return $this
150
     */
151
    public function assignData(DataObject $data)
152
    {
153
        parent::assignData($data);
154
155
        $oInfoInstance = $this->getInfoInstance();
156
157 View Code Duplication
        foreach ($this->aAssignKeys as $sKey) {
0 ignored issues
show
This code seems to be duplicated across your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
158
            $sData = $this->toolkitHelper->getAdditionalDataEntry($data, $sKey);
159
            if ($sData) {
0 ignored issues
show
Bug Best Practice introduced by
The expression $sData of type string|null is loosely compared to true; this is ambiguous if the string can be empty. You might want to explicitly use !== null instead.

In PHP, under loose comparison (like ==, or !=, or switch conditions), values of different types might be equal.

For string values, the empty string '' is a special case, in particular the following results might be unexpected:

''   == false // true
''   == null  // true
'ab' == false // false
'ab' == null  // false

// It is often better to use strict comparison
'' === false // false
'' === null  // false
Loading history...
160
                $oInfoInstance->setAdditionalInformation($sKey, $sData);
161
            }
162
        }
163
164
        $sFormattedDob = $this->getFormattedBirthday($data);
165
        if ($sFormattedDob !== false) {
166
            $oInfoInstance->setAdditionalInformation('dob', $sFormattedDob);
167
        }
168
169
        return $this;
170
    }
171
}
172