Issues in HttpPostBinding.php (master) - Issues in master - thephplab/lightsaml - Measure and Improve Code Quality continuously with Scrutinizer

Issues (1208)

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.

src/LightSaml/Binding/HttpPostBinding.php (5 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

/*
 * This file is part of the LightSAML-Core package.
 *
 * (c) Milos Tomic <[email protected]>
 *
 * This source file is subject to the MIT license that is bundled
 * with this source code in the file LICENSE.
 */

namespace LightSaml\Binding;

use LightSaml\Context\Profile\Helper\MessageContextHelper;
use LightSaml\Context\Profile\MessageContext;
use LightSaml\Error\LightSamlBindingException;
use LightSaml\Model\Protocol\AbstractRequest;
use LightSaml\Model\Protocol\SamlMessage;
use Symfony\Component\HttpFoundation\Request;

class HttpPostBinding extends AbstractBinding
{
    /**
     * @param MessageContext $context
     * @param null|string    $destination
     *
     * @return SamlPostResponse
     */
    public function send(MessageContext $context, $destination = null)
    {
        $message = MessageContextHelper::asSamlMessage($context);
        $destination = $message->getDestination() ? $message->getDestination() : $destination;

        $serializationContext = $context->getSerializationContext();
        $message->serialize($serializationContext->getDocument(), $serializationContext);
function acceptsInteger($int) { }

$x = '123'; // string "123"

// Instead of
acceptsInteger($x);

// we recommend to use
acceptsInteger((integer) $x);
        $msgStr = $serializationContext->getDocument()->saveXML();


        $this->dispatchSend($msgStr);

        $msgStr = base64_encode($msgStr);

        $type = $message instanceof AbstractRequest ? 'SAMLRequest' : 'SAMLResponse';

        $data = array($type => $msgStr);
        if ($message->getRelayState()) {
''   == false // true
''   == null  // true
'ab' == false // false
'ab' == null  // false

// It is often better to use strict comparison
'' === false // false
'' === null  // false
            $data['RelayState'] = $message->getRelayState();
        }

        $result = new SamlPostResponse($destination, $data);
        $result->renderContent();

        return $result;
    }

    /**
     * @param Request        $request
     * @param MessageContext $context
     */
    public function receive(Request $request, MessageContext $context)
    {
        $post = $request->request->all();
        if (array_key_exists('SAMLRequest', $post)) {
            $msg = $post['SAMLRequest'];
        } elseif (array_key_exists('SAMLResponse', $post)) {
            $msg = $post['SAMLResponse'];
        } else {
            throw new LightSamlBindingException('Missing SAMLRequest or SAMLResponse parameter');
        }

        $msg = base64_decode($msg);

        $this->dispatchReceive($msg);

        $deserializationContext = $context->getDeserializationContext();
        $result = SamlMessage::fromXML($msg, $deserializationContext);
function acceptsInteger($int) { }

$x = '123'; // string "123"

// Instead of
acceptsInteger($x);

// we recommend to use
acceptsInteger((integer) $x);

        if (array_key_exists('RelayState', $post)) {
            $result->setRelayState($post['RelayState']);
        }

        $context->setMessage($result);
    }
}


1		<?php
2
3		/*
4		* This file is part of the LightSAML-Core package.
5		*
6		* (c) Milos Tomic <[email protected]>
7		*
8		* This source file is subject to the MIT license that is bundled
9		* with this source code in the file LICENSE.
10		*/
11
12		namespace LightSaml\Binding;
13
14		use LightSaml\Context\Profile\Helper\MessageContextHelper;
15		use LightSaml\Context\Profile\MessageContext;
16		use LightSaml\Error\LightSamlBindingException;
17		use LightSaml\Model\Protocol\AbstractRequest;
18		use LightSaml\Model\Protocol\SamlMessage;
19		use Symfony\Component\HttpFoundation\Request;
20
21		class HttpPostBinding extends AbstractBinding
22		{
23		/**
24		* @param MessageContext $context
25		* @param null\|string $destination
26		*
27		* @return SamlPostResponse
28		*/
29	4	public function send(MessageContext $context, $destination = null)
30		{
31	4	$message = MessageContextHelper::asSamlMessage($context);
32	4	$destination = $message->getDestination() ? $message->getDestination() : $destination;
33
34	4	$serializationContext = $context->getSerializationContext();
35	4	$message->serialize($serializationContext->getDocument(), $serializationContext);
		0 ignored issues – show Bug introduced 2020-07-28 16:14 UTC by Report Bug Copy Issue Report Show Similar Issues like this The method `getDocument()` does not seem to exist on `object<LightSaml\Context\ContextInterface>`. This check looks for calls to methods that do not seem to exist on a given type. It looks for the method on the type itself as well as in inherited classes or implemented interfaces. This is most likely a typographical error or the method has been renamed. Loading history... Documentation introduced 2020-07-28 16:14 UTC by Report Bug Copy Issue Report Show Similar Issues like this `$serializationContext` is of type `object<LightSaml\Context\ContextInterface>\|null`, but the function expects a `object<LightSaml\Model\C...t\SerializationContext>`. It seems like the type of the argument is not accepted by the function/method which you are calling. In some cases, in particular if PHP’s automatic type-juggling kicks in this might be fine. In other cases, however this might be a bug. We suggest to add an explicit type cast like in the following example: function acceptsInteger($int) { } $x = '123'; // string "123" // Instead of acceptsInteger($x); // we recommend to use acceptsInteger((integer) $x); Loading history...
36	4	$msgStr = $serializationContext->getDocument()->saveXML();
		0 ignored issues – show Bug introduced 2020-07-28 16:14 UTC by Report Bug Copy Issue Report Show Similar Issues like this The method `getDocument()` does not seem to exist on `object<LightSaml\Context\ContextInterface>`. This check looks for calls to methods that do not seem to exist on a given type. It looks for the method on the type itself as well as in inherited classes or implemented interfaces. This is most likely a typographical error or the method has been renamed. Loading history...
37
38	4	$this->dispatchSend($msgStr);
39
40	4	$msgStr = base64_encode($msgStr);
41
42	4	$type = $message instanceof AbstractRequest ? 'SAMLRequest' : 'SAMLResponse';
43
44	4	$data = array($type => $msgStr);
45	4	if ($message->getRelayState()) {
		0 ignored issues – show Bug Best Practice introduced 2020-07-28 16:14 UTC by Report Bug Copy Issue Report Show Similar Issues like this The expression `$message->getRelayState()` 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...
46	2	$data['RelayState'] = $message->getRelayState();
47		}
48
49	4	$result = new SamlPostResponse($destination, $data);
50	4	$result->renderContent();
51
52	4	return $result;
53		}
54
55		/**
56		* @param Request $request
57		* @param MessageContext $context
58		*/
59	3	public function receive(Request $request, MessageContext $context)
60		{
61	3	$post = $request->request->all();
62	3	if (array_key_exists('SAMLRequest', $post)) {
63	1	$msg = $post['SAMLRequest'];
64	2	} elseif (array_key_exists('SAMLResponse', $post)) {
65	1	$msg = $post['SAMLResponse'];
66		} else {
67	1	throw new LightSamlBindingException('Missing SAMLRequest or SAMLResponse parameter');
68		}
69
70	2	$msg = base64_decode($msg);
71
72	2	$this->dispatchReceive($msg);
73
74	2	$deserializationContext = $context->getDeserializationContext();
75	2	$result = SamlMessage::fromXML($msg, $deserializationContext);
		0 ignored issues – show Documentation introduced 2020-07-28 16:14 UTC by Report Bug Copy Issue Report Show Similar Issues like this `$deserializationContext` is of type `object<LightSaml\Context\ContextInterface>\|null`, but the function expects a `object<LightSaml\Model\C...DeserializationContext>`. It seems like the type of the argument is not accepted by the function/method which you are calling. In some cases, in particular if PHP’s automatic type-juggling kicks in this might be fine. In other cases, however this might be a bug. We suggest to add an explicit type cast like in the following example: function acceptsInteger($int) { } $x = '123'; // string "123" // Instead of acceptsInteger($x); // we recommend to use acceptsInteger((integer) $x); Loading history...
76
77	2	if (array_key_exists('RelayState', $post)) {
78	1	$result->setRelayState($post['RelayState']);
79		}
80
81	2	$context->setMessage($result);
82	2	}
83		}
84

thephplab / lightsaml

Issues (1208)

Security Analysis not enabled

src/LightSaml/Binding/HttpPostBinding.php (5 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like