Issues (557)

Security Analysis    not enabled

This project does not seem to handle request data directly as such no vulnerable execution paths were found.

  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.
  Regex Injection
Regex Injection enables an attacker to execute arbitrary code in your PHP process.
  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.
  Response Splitting
Response Splitting can be used to send arbitrary responses.
  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.
  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.
  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.
  Code Injection
Code Injection enables an attacker to execute arbitrary code on the server.
  Variable Injection
Variable Injection enables an attacker to overwrite program variables with custom data, and can lead to further vulnerabilities.
  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.
  Other Vulnerability
This category comprises other attack vectors such as manipulating the PHP runtime, loading custom extensions, freezing the runtime, or similar.
  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.
  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.
  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.
  Header Injection
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/Phing/Io/OutputStream.php (1 issue)

Labels
Severity
1
<?php
2
3
/**
4
 * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
5
 * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
6
 * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
7
 * A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
8
 * OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
9
 * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
10
 * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
11
 * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
12
 * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
13
 * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
14
 * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
15
 *
16
 * This software consists of voluntary contributions made by many individuals
17
 * and is licensed under the LGPL. For more information please see
18
 * <http://phing.info>.
19
 */
20
21
namespace Phing\Io;
22
23
/**
24
 * Wrapper class for PHP stream that supports write operations.
25
 */
26
class OutputStream
27
{
28
    /**
29
     * @var resource the configured PHP stream
30
     */
31
    protected $stream;
32
33
    /**
34
     * Construct a new OutputStream.
35
     *
36
     * @param resource $stream configured PHP stream for writing
37
     *
38
     * @throws IOException
39
     */
40 59
    public function __construct($stream)
41
    {
42 59
        if (!is_resource($stream)) {
43
            throw new IOException('Passed argument is not a valid stream.');
44
        }
45 59
        $this->stream = $stream;
46
    }
47
48
    /**
49
     * Returns a string representation of the attached PHP stream.
50
     *
51
     * @return string
52
     */
53
    public function __toString()
54
    {
55
        return (string) $this->stream;
56
    }
57
58
    /**
59
     * Closes attached stream, flushing output first.
60
     *
61
     * @throws IOException if cannot close stream (note that attempting to close an already closed stream will not raise an IOException)
62
     */
63 49
    public function close()
64
    {
65 49
        if (null === $this->stream) {
66 1
            return;
67
        }
68 49
        $this->flush();
69 49
        error_clear_last();
70 49
        if (false === @fclose($this->stream)) {
71
            $lastError = error_get_last();
72
            $errormsg = $lastError['message'];
73
            $metaData = stream_get_meta_data($this->stream);
74
            $resource = $metaData['uri'];
75
            $msg = 'Cannot close ' . $resource . ": {$errormsg}";
76
77
            throw new IOException($msg);
78
        }
79 49
        $this->stream = null;
80
    }
81
82
    /**
83
     * Flushes stream.
84
     *
85
     * @throws IOException if unable to flush data (e.g. stream is not open).
86
     */
87 50
    public function flush()
88
    {
89 50
        error_clear_last();
90 50
        if (null === $this->stream || false === @fflush($this->stream)) {
91 1
            $lastError = error_get_last();
92 1
            $errormsg = $lastError['message'] ?? 'no stream';
93
94 1
            throw new IOException('Could not flush stream: ' . $errormsg);
95
        }
96
    }
97
98
    /**
99
     * Writes data to stream.
100
     *
101
     * @param string $buf binary/character data to write
102
     * @param int    $off (Optional) offset
103
     * @param int    $len (Optional) number of bytes/chars to write
104
     *
105
     * @throws IOException - if there is an error writing to stream
106
     */
107 57
    public function write($buf, $off = null, $len = null)
108
    {
109 57
        if (null === $off && null === $len) {
110 57
            $to_write = $buf;
111 1
        } elseif (null !== $off && null === $len) {
112 1
            $to_write = substr($buf, $off);
113 1
        } elseif (null === $off && null !== $len) {
114
            $to_write = substr($buf, 0, $len);
115
        } else {
116 1
            $to_write = substr($buf, $off, $len);
0 ignored issues
show
It seems like $off can also be of type null; however, parameter $offset of substr() does only seem to accept integer, maybe add an additional type check? ( Ignorable by Annotation )

If this is a false-positive, you can also ignore this issue in your code via the ignore-type  annotation

116
            $to_write = substr($buf, /** @scrutinizer ignore-type */ $off, $len);
Loading history...
117
        }
118
119 57
        $result = @fwrite($this->stream, $to_write);
120
121 57
        if (false === $result) {
122
            throw new IOException('Error writing to stream.');
123
        }
124
    }
125
}
126