Issues (538)

Security Analysis    no request data  

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

  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.
  Regex Injection
Regex Injection enables an attacker to execute arbitrary code in your PHP process.
  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.
  Response Splitting
Response Splitting can be used to send arbitrary responses.
  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.
  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.
  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.
  Code Injection
Code Injection enables an attacker to execute arbitrary code on the server.
  Variable Injection
Variable Injection enables an attacker to overwrite program variables with custom data, and can lead to further vulnerabilities.
  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.
  Other Vulnerability
This category comprises other attack vectors such as manipulating the PHP runtime, loading custom extensions, freezing the runtime, or similar.
  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.
  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.
  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.
  Header Injection
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/XML/saml/Issuer.php (2 issues)

1
<?php
2
3
declare(strict_types=1);
4
5
namespace SimpleSAML\SAML2\XML\saml;
6
7
use SimpleSAML\SAML2\Assert\Assert;
8
use SimpleSAML\SAML2\Constants as C;
0 ignored issues
show
The type SimpleSAML\SAML2\Constants was not found. Maybe you did not declare it correctly or list all dependencies?

The issue could also be caused by a filter entry in the build configuration. If the path has been excluded in your configuration, e.g. excluded_paths: ["lib/*"], you can move it to the dependency path list as follows:

filter:
    dependency_paths: ["lib/*"]

For further information see https://scrutinizer-ci.com/docs/tools/php/php-scrutinizer/#list-dependency-paths

Loading history...
9
use SimpleSAML\SAML2\Exception\ProtocolViolationException;
10
use SimpleSAML\SAML2\Type\SAMLAnyURIValue;
11
use SimpleSAML\SAML2\Type\SAMLStringValue;
12
use SimpleSAML\XML\SchemaValidatableElementInterface;
13
use SimpleSAML\XML\SchemaValidatableElementTrait;
14
15
/**
16
 * Class representing the saml:Issuer element.
17
 *
18
 * @package simplesamlphp/saml2
19
 */
20
final class Issuer extends NameIDType implements SchemaValidatableElementInterface
0 ignored issues
show
The type SimpleSAML\SAML2\XML\saml\NameIDType was not found. Maybe you did not declare it correctly or list all dependencies?

The issue could also be caused by a filter entry in the build configuration. If the path has been excluded in your configuration, e.g. excluded_paths: ["lib/*"], you can move it to the dependency path list as follows:

filter:
    dependency_paths: ["lib/*"]

For further information see https://scrutinizer-ci.com/docs/tools/php/php-scrutinizer/#list-dependency-paths

Loading history...
21
{
22
    use SchemaValidatableElementTrait;
23
24
25
    /**
26
     * Initialize a saml:Issuer
27
     *
28
     * @param \SimpleSAML\SAML2\Type\SAMLStringValue $value
29
     * @param \SimpleSAML\SAML2\Type\SAMLStringValue|null $NameQualifier
30
     * @param \SimpleSAML\SAML2\Type\SAMLStringValue|null $SPNameQualifier
31
     * @param \SimpleSAML\SAML2\Type\SAMLAnyURIValue|null $Format
32
     * @param \SimpleSAML\SAML2\Type\SAMLStringValue|null $SPProvidedID
33
     */
34
    public function __construct(
35
        SAMLStringValue $value,
36
        ?SAMLStringValue $NameQualifier = null,
37
        ?SAMLStringValue $SPNameQualifier = null,
38
        ?SAMLAnyURIValue $Format = null,
39
        ?SAMLStringValue $SPProvidedID = null,
40
    ) {
41
        /**
42
         * The format of this NameIDType.
43
         *
44
         * Defaults to urn:oasis:names:tc:SAML:2.0:nameid-format:entity:
45
         *
46
         * Indicates that the content of the element is the identifier of an entity that provides SAML-based services
47
         * (such as a SAML authority, requester, or responder) or is a participant in SAML profiles (such as a service
48
         * provider supporting the browser SSO profile). Such an identifier can be used in the <Issuer> element to
49
         * identify the issuer of a SAML request, response, or assertion, or within the <NameID> element to make
50
         * assertions about system entities that can issue SAML requests, responses, and assertions. It can also be
51
         * used in other elements and attributes whose purpose is to identify a system entity in various protocol
52
         * exchanges.
53
         *
54
         * The syntax of such an identifier is a URI of not more than 1024 characters in length. It is RECOMMENDED that
55
         * a system entity use a URL containing its own domain name to identify itself.
56
         *
57
         * @see saml-core-2.0-os
58
         *
59
         * From saml-core-2.0-os 8.3.6, when the entity Format is used: "The NameQualifier, SPNameQualifier, and
60
         * SPProvidedID attributes MUST be omitted."
61
         */
62
        if ($Format === null || $Format->getValue() === C::NAMEID_ENTITY) {
63
            Assert::allNull(
64
                [$NameQualifier, $SPNameQualifier, $SPProvidedID],
65
                'Illegal combination of attributes being used',
66
            );
67
68
            Assert::validEntityID($value->getValue(), ProtocolViolationException::class);
69
        }
70
71
        parent::__construct($value, $NameQualifier, $SPNameQualifier, $Format, $SPProvidedID);
72
    }
73
}
74