Issues (369)

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.

lib/classes/Swift/Attachment.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
/*
4
 * This file is part of SwiftMailer.
5
 * (c) 2004-2009 Chris Corbyn
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
/**
12
 * Attachment class for attaching files to a {@link Swift_Mime_Message}.
13
 *
14
 * @author Chris Corbyn
15
 */
16
class Swift_Attachment extends Swift_Mime_Attachment
0 ignored issues
show
Coding Style Compatibility introduced by
PSR1 recommends that each class must be in a namespace of at least one level to avoid collisions.

You can fix this by adding a namespace to your class:

namespace YourVendor;

class YourClass { }

When choosing a vendor namespace, try to pick something that is not too generic to avoid conflicts with other libraries.

Loading history...
17
{
18
    /**
19
     * Create a new Attachment.
20
     *
21
     * Details may be optionally provided to the constructor.
22
     *
23
     * @param string|Swift_OutputByteStream $data
24
     * @param string                        $filename
25
     * @param string                        $contentType
26
     */
27 32
    public function __construct($data = null, $filename = null, $contentType = null)
28
    {
29 32
        call_user_func_array(
30 32
            array($this, 'Swift_Mime_Attachment::__construct'),
31 32
            Swift_DependencyContainer::getInstance()->createDependenciesFor('mime.attachment')
32 32
        );
33
34 32
        $this->setBody($data);
35 32
        $this->setFilename($filename);
36 32
        if ($contentType) {
0 ignored issues
show
Bug Best Practice introduced by
The expression $contentType 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...
37 1
            $this->setContentType($contentType);
38 1
        }
39 32
    }
40
41
    /**
42
     * Create a new Attachment.
43
     *
44
     * @param string|Swift_OutputByteStream $data
45
     * @param string                        $filename
46
     * @param string                        $contentType
47
     *
48
     * @return Swift_Mime_Attachment
49
     */
50
    public static function newInstance($data = null, $filename = null, $contentType = null)
51
    {
52
        return new self($data, $filename, $contentType);
53
    }
54
55
    /**
56
     * Create a new Attachment from a filesystem path.
57
     *
58
     * @param string $path
59
     * @param string $contentType optional
60
     *
61
     * @return Swift_Mime_Attachment
62
     */
63 10
    public static function fromPath($path, $contentType = null)
64
    {
65 10
        $self = new self();
66 10
        return $self->setFile(
67 10
            new Swift_ByteStream_FileByteStream($path),
68
            $contentType
69 9
        );
70
    }
71
}
72