Issues in Detector.php (develop) - Issues in develop - cwd/bounce-detection - Measure and Improve Code Quality continuously with Scrutinizer

Issues (1)

Security Analysis no request data

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/Detector.php (1 issue)

Labels

Unused Code 1

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
/*
 * This file is part of Bounce-Detection.
 *
 * (c)2016 cwd.at GmbH <[email protected]>
 *
 * For the full copyright and license information, please view the LICENSE
 * file that was distributed with this source code.
 */

namespace Cwd\BounceDetection;
use PhpMimeMailParser\Parser;

/**
 * Class Detector
 *
 * @package Cwd\BounceDetection
 * @author  Ludwig Ruderstaller <[email protected]>
 */
class Detector
{
    /**
     * @var RuleConfig|null
     */
    protected $ruleConfig = null;

    public function __construct($ruleFile = null)
    {
        $this->ruleConfig = RuleFactory::getRules($ruleFile);
    }

    /**
     * @param string $mail
     *
     * @return array
     */
    public function testAll($mail)
    {
        $result = $this->testRulesAgainst($this->ruleConfig->getDSNRules(), $mail);

        if ($result === null) {
            $result = $this->testRulesAgainst($this->ruleConfig->getBodyRules(), $mail);
        }

        if ($result === null) {
if (rand(1, 6) > 3) {
//print "Check failed";
} else {
    print "Check succeeded";
}
            // @todo
        }

        $result['email'] = $this->findEmail($mail);

        return $result;
    }

    /**
     * @param $mail
     *
     * @return string
     */
    public function findEmail($mail)
    {
        foreach ($this->ruleConfig->getEmailRules() as $rule) {
            if (preg_match($rule['regexp'], $mail, $match)) {
                return $match[1];
            }
        }

        return null;
    }

    /**
     * @param array  $rules
     * @param string $mail
     *
     * @return array
     */
    public function testRulesAgainst(array $rules, $mail)
    {
        $parser = new Parser();
        $parser->setText($mail);
        $data = $parser->getData();

        foreach ($rules as $rule) {
            if (preg_match($rule['regexp'], $data, $match)) {
                $result = [
                    'rule_cat' => $rule['category'],
                    'rule_no'  => $rule['number'],
                ];

                if (isset($rule['idx_email'])) {
                    $result['email'] = $match[$rule['idx_email']];
                }

                return $result;
            }
        }
    }
}


1		<?php
2		/*
3		* This file is part of Bounce-Detection.
4		*
5		* (c)2016 cwd.at GmbH <[email protected]>
6		*
7		* For the full copyright and license information, please view the LICENSE
8		* file that was distributed with this source code.
9		*/
10
11		namespace Cwd\BounceDetection;
12		use PhpMimeMailParser\Parser;
13
14		/**
15		* Class Detector
16		*
17		* @package Cwd\BounceDetection
18		* @author Ludwig Ruderstaller <[email protected]>
19		*/
20		class Detector
21		{
22		/**
23		* @var RuleConfig\|null
24		*/
25		protected $ruleConfig = null;
26
27		public function __construct($ruleFile = null)
28		{
29		$this->ruleConfig = RuleFactory::getRules($ruleFile);
30		}
31
32		/**
33		* @param string $mail
34		*
35		* @return array
36		*/
37	247	public function testAll($mail)
38		{
39	247	$result = $this->testRulesAgainst($this->ruleConfig->getDSNRules(), $mail);
40
41	247	if ($result === null) {
42	18	$result = $this->testRulesAgainst($this->ruleConfig->getBodyRules(), $mail);
43	18	}
44
45	247	if ($result === null) {
		0 ignored issues – show Unused Code introduced 2016-10-08 17:07 UTC by Report Bug Copy Issue Report Show Similar Issues like this This `if` statement is empty and can be removed. This check looks for the bodies of `if` statements that have no statements or where all statements have been commented out. This may be the result of changes for debugging or the code may simply be obsolete. These `if` bodies can be removed. If you have an empty if but statements in the `else` branch, consider inverting the condition. if (rand(1, 6) > 3) { //print "Check failed"; } else { print "Check succeeded"; } could be turned into if (rand(1, 6) <= 3) { print "Check succeeded"; } This is much more concise to read. Loading history...
46		// @todo
47	18	}
48
49	247	$result['email'] = $this->findEmail($mail);
50
51	247	return $result;
52		}
53
54		/**
55		* @param $mail
56		*
57		* @return string
58		*/
59	247	public function findEmail($mail)
60		{
61	247	foreach ($this->ruleConfig->getEmailRules() as $rule) {
62	247	if (preg_match($rule['regexp'], $mail, $match)) {
63	134	return $match[1];
64		}
65	216	}
66
67	113	return null;
68		}
69
70		/**
71		* @param array $rules
72		* @param string $mail
73		*
74		* @return array
75		*/
76	247	public function testRulesAgainst(array $rules, $mail)
77		{
78	247	$parser = new Parser();
79	247	$parser->setText($mail);
80	247	$data = $parser->getData();
81
82	247	foreach ($rules as $rule) {
83	247	if (preg_match($rule['regexp'], $data, $match)) {
84		$result = [
85	229	'rule_cat' => $rule['category'],
86	229	'rule_no' => $rule['number'],
87	229	];
88
89	229	if (isset($rule['idx_email'])) {
90		$result['email'] = $match[$rule['idx_email']];
91		}
92
93	229	return $result;
94		}
95	242	}
96	18	}
97		}
98

cwd / bounce-detection

Issues (1)

Security Analysis no request data

src/Detector.php (1 issue)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like