Issues in Tweet.php (master) - Issues in master - php-api-clients/twitter - Measure and Improve Code Quality continuously with Scrutinizer

Issues (40)

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/Resource/Tweet.php (8 issues)

Labels

Bug 8

Severity

Major 8

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 declare(strict_types=1);

namespace ApiClients\Client\Twitter\Resource;

use ApiClients\Foundation\Hydrator\Annotation\EmptyResource;
use ApiClients\Foundation\Hydrator\Annotation\Nested;
use ApiClients\Foundation\Resource\AbstractResource;
use DateTime;

/**
 * @Nested(
 *     user="User"
 * )
 * @EmptyResource("EmptyTweet")
 */
abstract class Tweet extends AbstractResource implements TweetInterface
{
    /**
     * @var bool
     */
    protected $favorited;

    /**
     * @var bool
     */
    protected $truncated;

    /**
     * @var DateTime
     */
    protected $created_at;

    /**
     * @var string
     */
    protected $id_str;

    /**
     * @var string
     */
    //protected $in_reply_to_user_id_str;

    /**
     * @var array
     */
    protected $contributors;

    /**
     * @var string
     */
    protected $text;

    /**
     * @var int
     */
    //protected $retweet_count;

    /**
     * @var string
     */
    //protected $in_reply_to_status_id_str;

    /**
     * @var int
     */
    protected $id;

    /**
     * @var bool
     */
    protected $retweeted;

    /**
     * @var bool
     */
    //protected $possibly_sensitive;

    /**
     * @var int
     */
    //protected $in_reply_to_user_id;

    /**
     * @var User
     */
    protected $user;

    /**
     * @var string
     */
    //protected $in_reply_to_screen_name;

    /**
     * @var string
     */
    //protected $source;

    /**
     * @var int
     */
    //protected $in_reply_to_status_id;

    /**
     * @return bool
     */
    public function favorited(): bool
    {
        return $this->favorited;
    }

    /**
     * @return bool
     */
    public function truncated(): bool
    {
        return $this->truncated;
    }

    /**
     * @return DateTime
     */
    public function createdAt(): DateTime
    {
        return $this->created_at;
    }

    /**
     * @return string
     */
    public function idStr(): string
    {
        return $this->id_str;
    }

    /**
     * @return string
     */
    public function inReplyToUserIdStr(): string
    {
        return $this->in_reply_to_user_id_str;

    }

    /**
     * @return array
     */
    public function contributors(): array
    {
        return $this->contributors;
    }

    /**
     * @return string
     */
    public function text(): string
    {
        return $this->text;
    }

    /**
     * @return int
     */
    public function retweetCount(): int
    {
        return $this->retweet_count;
class MyClass { }

$x = new MyClass();
$x->foo = true;
    }

    /**
     * @return string
     */
    public function inReplyToStatusIdStr(): string
    {
        return $this->in_reply_to_status_id_str;

    }

    /**
     * @return int
     */
    public function id(): int
    {
        return $this->id;
    }

    /**
     * @return bool
     */
    public function retweeted(): bool
    {
        return $this->retweeted;
    }

    /**
     * @return bool
     */
    public function possiblySensitive(): bool
    {
        return $this->possibly_sensitive;
class MyClass { }

$x = new MyClass();
$x->foo = true;
    }

    /**
     * @return int
     */
    public function inReplyToUserId(): int
    {
        return $this->in_reply_to_user_id;
class MyClass { }

$x = new MyClass();
$x->foo = true;
    }

    /**
     * @return User
     */
    public function user(): User
    {
        return $this->user;
    }

    /**
     * @return string
     */
    public function inReplyToScreenName(): string
    {
        return $this->in_reply_to_screen_name;
class MyClass { }

$x = new MyClass();
$x->foo = true;
    }

    /**
     * @return string
     */
    public function source(): string
    {
        return $this->source;
class MyClass { }

$x = new MyClass();
$x->foo = true;
    }

    /**
     * @return int
     */
    public function inReplyToStatusId(): int
    {
        return $this->in_reply_to_status_id;
class MyClass { }

$x = new MyClass();
$x->foo = true;
    }
}


GitHub Access Token became invalid

Issues (40)

Security Analysis no request data

src/Resource/Tweet.php (8 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

1		<?php declare(strict_types=1);
2
3		namespace ApiClients\Client\Twitter\Resource;
4
5		use ApiClients\Foundation\Hydrator\Annotation\EmptyResource;
6		use ApiClients\Foundation\Hydrator\Annotation\Nested;
7		use ApiClients\Foundation\Resource\AbstractResource;
8		use DateTime;
9
10		/**
11		* @Nested(
12		* user="User"
13		* )
14		* @EmptyResource("EmptyTweet")
15		*/
16		abstract class Tweet extends AbstractResource implements TweetInterface
17		{
18		/**
19		* @var bool
20		*/
21		protected $favorited;
22
23		/**
24		* @var bool
25		*/
26		protected $truncated;
27
28		/**
29		* @var DateTime
30		*/
31		protected $created_at;
32
33		/**
34		* @var string
35		*/
36		protected $id_str;
37
38		/**
39		* @var string
40		*/
41		//protected $in_reply_to_user_id_str;
42
43		/**
44		* @var array
45		*/
46		protected $contributors;
47
48		/**
49		* @var string
50		*/
51		protected $text;
52
53		/**
54		* @var int
55		*/
56		//protected $retweet_count;
57
58		/**
59		* @var string
60		*/
61		//protected $in_reply_to_status_id_str;
62
63		/**
64		* @var int
65		*/
66		protected $id;
67
68		/**
69		* @var bool
70		*/
71		protected $retweeted;
72
73		/**
74		* @var bool
75		*/
76		//protected $possibly_sensitive;
77
78		/**
79		* @var int
80		*/
81		//protected $in_reply_to_user_id;
82
83		/**
84		* @var User
85		*/
86		protected $user;
87
88		/**
89		* @var string
90		*/
91		//protected $in_reply_to_screen_name;
92
93		/**
94		* @var string
95		*/
96		//protected $source;
97
98		/**
99		* @var int
100		*/
101		//protected $in_reply_to_status_id;
102
103		/**
104		* @return bool
105		*/
106	4	public function favorited(): bool
107		{
108	4	return $this->favorited;
109		}
110
111		/**
112		* @return bool
113		*/
114	4	public function truncated(): bool
115		{
116	4	return $this->truncated;
117		}
118
119		/**
120		* @return DateTime
121		*/
122		public function createdAt(): DateTime
123		{
124		return $this->created_at;
125		}
126
127		/**
128		* @return string
129		*/
130	4	public function idStr(): string
131		{
132	4	return $this->id_str;
133		}
134
135		/**
136		* @return string
137		*/
138		public function inReplyToUserIdStr(): string
139		{
140		return $this->in_reply_to_user_id_str;
		0 ignored issues – show Bug introduced 2016-12-07 22:11 UTC by Report Bug Copy Issue Report Show Similar Issues like this The property `in_reply_to_user_id_str` does not seem to exist. Did you mean `id_str`? An attempt at access to an undefined property has been detected. This may either be a typographical error or the property has been renamed but there are still references to its old name. If you really want to allow access to undefined properties, you can define magic methods to allow access. See the php core documentation on Overloading. Loading history...
141		}
142
143		/**
144		* @return array
145		*/
146		public function contributors(): array
147		{
148		return $this->contributors;
149		}
150
151		/**
152		* @return string
153		*/
154	4	public function text(): string
155		{
156	4	return $this->text;
157		}
158
159		/**
160		* @return int
161		*/
162		public function retweetCount(): int
163		{
164		return $this->retweet_count;
		0 ignored issues – show Bug introduced 2016-12-07 22:11 UTC by Report Bug Copy Issue Report Show Similar Issues like this The property `retweet_count` does not exist. Did you maybe forget to declare it? In PHP it is possible to write to properties without declaring them. For example, the following is perfectly valid PHP code: class MyClass { } $x = new MyClass(); $x->foo = true; Generally, it is a good practice to explictly declare properties to avoid accidental typos and provide IDE auto-completion: class MyClass { public $foo; } $x = new MyClass(); $x->foo = true; Loading history...
165		}
166
167		/**
168		* @return string
169		*/
170		public function inReplyToStatusIdStr(): string
171		{
172		return $this->in_reply_to_status_id_str;
		0 ignored issues – show Bug introduced 2016-12-07 22:11 UTC by Report Bug Copy Issue Report Show Similar Issues like this The property `in_reply_to_status_id_str` does not seem to exist. Did you mean `id_str`? An attempt at access to an undefined property has been detected. This may either be a typographical error or the property has been renamed but there are still references to its old name. If you really want to allow access to undefined properties, you can define magic methods to allow access. See the php core documentation on Overloading. Loading history...
173		}
174
175		/**
176		* @return int
177		*/
178	4	public function id(): int
179		{
180	4	return $this->id;
181		}
182
183		/**
184		* @return bool
185		*/
186	4	public function retweeted(): bool
187		{
188	4	return $this->retweeted;
189		}
190
191		/**
192		* @return bool
193		*/
194		public function possiblySensitive(): bool
195		{
196		return $this->possibly_sensitive;
		0 ignored issues – show Bug introduced 2016-12-07 22:11 UTC by Report Bug Copy Issue Report Show Similar Issues like this The property `possibly_sensitive` does not exist. Did you maybe forget to declare it? In PHP it is possible to write to properties without declaring them. For example, the following is perfectly valid PHP code: class MyClass { } $x = new MyClass(); $x->foo = true; Generally, it is a good practice to explictly declare properties to avoid accidental typos and provide IDE auto-completion: class MyClass { public $foo; } $x = new MyClass(); $x->foo = true; Loading history...
197		}
198
199		/**
200		* @return int
201		*/
202		public function inReplyToUserId(): int
203		{
204		return $this->in_reply_to_user_id;
		0 ignored issues – show Bug introduced 2016-12-07 22:11 UTC by Report Bug Copy Issue Report Show Similar Issues like this The property `in_reply_to_user_id` does not exist. Did you maybe forget to declare it? In PHP it is possible to write to properties without declaring them. For example, the following is perfectly valid PHP code: class MyClass { } $x = new MyClass(); $x->foo = true; Generally, it is a good practice to explictly declare properties to avoid accidental typos and provide IDE auto-completion: class MyClass { public $foo; } $x = new MyClass(); $x->foo = true; Loading history...
205		}
206
207		/**
208		* @return User
209		*/
210		public function user(): User
211		{
212		return $this->user;
213		}
214
215		/**
216		* @return string
217		*/
218		public function inReplyToScreenName(): string
219		{
220		return $this->in_reply_to_screen_name;
		0 ignored issues – show Bug introduced 2016-12-07 22:11 UTC by Report Bug Copy Issue Report Show Similar Issues like this The property `in_reply_to_screen_name` does not exist. Did you maybe forget to declare it? In PHP it is possible to write to properties without declaring them. For example, the following is perfectly valid PHP code: class MyClass { } $x = new MyClass(); $x->foo = true; Generally, it is a good practice to explictly declare properties to avoid accidental typos and provide IDE auto-completion: class MyClass { public $foo; } $x = new MyClass(); $x->foo = true; Loading history...
221		}
222
223		/**
224		* @return string
225		*/
226		public function source(): string
227		{
228		return $this->source;
		0 ignored issues – show Bug introduced 2016-12-07 22:11 UTC by Report Bug Copy Issue Report Show Similar Issues like this The property `source` does not exist. Did you maybe forget to declare it? In PHP it is possible to write to properties without declaring them. For example, the following is perfectly valid PHP code: class MyClass { } $x = new MyClass(); $x->foo = true; Generally, it is a good practice to explictly declare properties to avoid accidental typos and provide IDE auto-completion: class MyClass { public $foo; } $x = new MyClass(); $x->foo = true; Loading history...
229		}
230
231		/**
232		* @return int
233		*/
234		public function inReplyToStatusId(): int
235		{
236		return $this->in_reply_to_status_id;
		0 ignored issues – show Bug introduced 2016-12-07 22:11 UTC by Report Bug Copy Issue Report Show Similar Issues like this The property `in_reply_to_status_id` does not exist. Did you maybe forget to declare it? In PHP it is possible to write to properties without declaring them. For example, the following is perfectly valid PHP code: class MyClass { } $x = new MyClass(); $x->foo = true; Generally, it is a good practice to explictly declare properties to avoid accidental typos and provide IDE auto-completion: class MyClass { public $foo; } $x = new MyClass(); $x->foo = true; Loading history...
237		}
238		}
239

php-api-clients / twitter

GitHub Access Token became invalid

Issues (40)

Security Analysis no request data

src/Resource/Tweet.php (8 issues)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like