Issues (18)

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

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
 * This file is part of the NeedleProject\FileIo package.
4
 *
5
 * For the full copyright and license information, please view the LICENSE
6
 * file that was distributed with this source code.
7
 */
8
namespace NeedleProject\FileIo\Helper;
9
10
use NeedleProject\FileIo\File;
11
12
/**
13
 * Class PathHelper
14
 *
15
 * @package NeedleProject\FileIo\Helper
16
 * @author Adrian Tilita <[email protected]>
17
 * @copyright 2017 Adrian Tilita
18
 * @license https://opensource.org/licenses/MIT MIT Licence
19
 */
20
class PathHelper
21
{
22
    /**
23
     * Convert path separator to the system's default separator
24
     *
25
     * For example:
26
     * root\\foo/bar\ becomes root:
27
     * - \\foo\\bar on Windows and
28
     * - /root/foo/bar on Linux
29
     *
30
     * @param string $path
31
     * @return string
32
     */
33 54
    public function normalizePathSeparator($path)
34
    {
35 54
        $path = preg_replace('#(\\\|\/)#', DIRECTORY_SEPARATOR, $path);
0 ignored issues
show
Consider using a different name than the parameter $path. This often makes code more readable.
Loading history...
36 54
        return preg_replace('#' . DIRECTORY_SEPARATOR . '{2,}#', DIRECTORY_SEPARATOR, $path);
37
    }
38
39
    /**
40
     * Extract the the filename from a path
41
     *
42
     * Example: from /foo/bar/file.ext will result file.ext
43
     *
44
     * @param string $filePath
45
     * @return string
46
     */
47 53
    public function extractFilenameFromPath($filePath)
48
    {
49 53
        $fileParts = explode(DIRECTORY_SEPARATOR, $filePath);
50 53
        return array_pop($fileParts);
51
    }
52
53
    /**
54
     * Split a filename into an array containing the name and extension
55
     * Example:
56
     *  file.ext -> [file, ext]
57
     *  .htaccess -> ['', htaccess]
58
     *  name -> [name, '']
59
     *
60
     * @param string $filename
61
     * @return array
62
     */
63 52
    public function splitFilename($filename)
64
    {
65 52
        $extension = '';
66 52
        $name = $filename;
67 52
        if (false !== strpos($filename, File::EXTENSION_SEPARATOR)) {
68 36
            $filenameParts = explode(File::EXTENSION_SEPARATOR, $filename);
69 36
            $extension = array_pop($filenameParts);
70 36
            $name = implode(File::EXTENSION_SEPARATOR, $filenameParts);
71
        }
72
73
        return [
74 52
            $name,
75 52
            $extension
76
        ];
77
    }
78
}
79