Issues (3)

Security Analysis    no request data  

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.

src/Support/Domain.php (2 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
 * BrightNucleus ChainMail Component.
4
 *
5
 * @package   BrightNucleus/ChainMail
6
 * @author    Alain Schlesser <[email protected]>
7
 * @license   MIT
8
 * @link      http://www.brightnucleus.com/
9
 * @copyright 2016 Alain Schlesser, Bright Nucleus
10
 */
11
12
namespace BrightNucleus\ChainMail\Support;
13
14
use BrightNucleus\ChainMail\Exception\InvalidDomain;
15
16
/**
17
 * Class Domain.
18
 *
19
 * @since   1.0.0
20
 *
21
 * @package BrightNucleus\ChainMail
22
 * @author  Alain Schlesser <[email protected]>
23
 */
24
class Domain
25
{
26
27
    /**
28
     * Domain name.
29
     *
30
     * @var string
31
     */
32
    protected $domain;
33
34
    /**
35
     * Instantiate a Domain object.
36
     *
37
     * @param Domain|string $domain
38
     *
39
     * @throws InvalidDomain If the domain is not valid.
40
     */
41 9
    public function __construct($domain)
42
    {
43 9
        if ( ! $this->isValid($domain)) {
44 1
            throw InvalidDomain::from($domain);
0 ignored issues
show
It seems like $domain defined by parameter $domain on line 41 can also be of type object<BrightNucleus\ChainMail\Support\Domain>; however, BrightNucleus\ChainMail\...n\InvalidDomain::from() does only seem to accept string, maybe add an additional type check?

This check looks at variables that have been passed in as parameters and are passed out again to other methods.

If the outgoing method call has stricter type requirements than the method itself, an issue is raised.

An additional type check may prevent trouble.

Loading history...
45
        }
46
47 8
        $this->domain = (string)$domain;
48 8
    }
49
50
    /**
51
     * Return the domain name.
52
     *
53
     * @return string
54
     */
55 3
    public function getDomain()
56
    {
57 3
        return $this->domain;
58
    }
59
60
    /**
61
     * Reutrn a string representation of the Domain object.
62
     *
63
     * @return string
64
     */
65 3
    public function __toString()
66
    {
67 3
        return $this->getDomain();
68
    }
69
70
    /**
71
     * @param $domain
72
     *
73
     * @return bool
74
     */
75 9
    protected function isValid($domain)
76
    {
77
        // TODO: Implement real validation.
0 ignored issues
show
Coding Style Best Practice introduced by
Comments for TODO tasks are often forgotten in the code; it might be better to use a dedicated issue tracker.
Loading history...
78 9
        return $domain === trim($domain);
79
    }
80
}