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/InputByteStream.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
/*
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
 * An abstract means of writing data.
13
 *
14
 * Classes implementing this interface may use a subsystem which requires less
15
 * memory than working with large strings of data.
16
 *
17
 * @author Chris Corbyn
18
 */
19
interface Swift_InputByteStream
0 ignored issues
show
Coding Style Compatibility introduced by
Each interface must be in a namespace of at least one level (a top-level vendor name)

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...
20
{
21
    /**
22
     * Writes $bytes to the end of the stream.
23
     *
24
     * Writing may not happen immediately if the stream chooses to buffer.  If
25
     * you want to write these bytes with immediate effect, call {@link commit()}
26
     * after calling write().
27
     *
28
     * This method returns the sequence ID of the write (i.e. 1 for first, 2 for
29
     * second, etc etc).
30
     *
31
     * @param string $bytes
32
     *
33
     * @throws Swift_IoException
34
     *
35
     * @return int
36
     */
37
    public function write($bytes);
38
39
    /**
40
     * For any bytes that are currently buffered inside the stream, force them
41
     * off the buffer.
42
     *
43
     * @throws Swift_IoException
44
     */
45
    public function commit();
46
47
    /**
48
     * Attach $is to this stream.
49
     *
50
     * The stream acts as an observer, receiving all data that is written.
51
     * All {@link write()} and {@link flushBuffers()} operations will be mirrored.
52
     *
53
     * @param Swift_InputByteStream $is
54
     */
55
    public function bind(Swift_InputByteStream $is);
56
57
    /**
58
     * Remove an already bound stream.
59
     *
60
     * If $is is not bound, no errors will be raised.
61
     * If the stream currently has any buffered data it will be written to $is
62
     * before unbinding occurs.
63
     *
64
     * @param Swift_InputByteStream $is
65
     */
66
    public function unbind(Swift_InputByteStream $is);
67
68
    /**
69
     * Flush the contents of the stream (empty it) and set the internal pointer
70
     * to the beginning.
71
     */
72
    public function flushBuffers();
73
}
74