Issues (11)

Security Analysis    not enabled

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/Http/Controllers/SocialProvidersController.php (2 issues)

Labels
Severity

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
namespace Acacha\LaravelSocial\Http\Controllers;
4
5
use Acacha\LaravelSocial\Contracts\Factory as SocialProviderFactory;
6
use Acacha\LaravelSocial\Repositories\SocialUserRepository;
7
use Illuminate\Contracts\Auth\Factory as AuthFactory;
8
use Illuminate\Foundation\Auth\RedirectsUsers;
9
use Illuminate\Routing\Controller;
10
use Illuminate\Foundation\Bus\DispatchesJobs;
11
use Illuminate\Foundation\Validation\ValidatesRequests;
12
use Illuminate\Foundation\Auth\Access\AuthorizesRequests;
13
14
/**
15
 * Class SocialProvidersController.
16
 *
17
 * @package App\Http\Controllers
18
 */
19
class SocialProvidersController extends Controller
20
{
21
    use AuthorizesRequests, DispatchesJobs, ValidatesRequests, RedirectsUsers;
22
23
    /**
24
     * Laravel social provider factory.
25
     *
26
     * @var SocialProviderFactory
27
     */
28
    protected $socialProvider;
29
30
    /**
31
     * Laravel auth factory.
32
     *
33
     * @var \Illuminate\Contracts\Auth\Factory
34
     */
35
    protected $auth;
36
37
    /**
38
     * Where to redirect users after login/register.
39
     *
40
     * @var string
41
     */
42
    protected $redirectTo = '/home';
43
44
    /**
45
     * Social user repository.
46
     *
47
     * @var SocialUserRepository
48
     */
49
    protected $users;
50
51
    /**
52
     * SocialProvidersController constructor.
53
     *
54
     * @param SocialProviderFactory $socialProvider
55
     * @param AuthFactory $auth
56
     * @param SocialUserRepository $users
57
     */
58
    public function __construct(SocialProviderFactory $socialProvider, AuthFactory $auth, SocialUserRepository $users)
59
    {
60
        $this->socialProvider = $socialProvider;
61
        $this->auth = $auth;
62
        $this->users = $users;
63
    }
64
65
    /**
66
     * Redirect to social provider.
67
     *
68
     * @param $provider
69
     * @return \Symfony\Component\HttpFoundation\RedirectResponse
70
     */
71
    public function redirectToProvider($provider)
72
    {
73
        return $this->socialProvider->driver($provider)->redirect();
74
    }
75
76
    /**
77
     * Obtain the user information from social network.
78
     *
79
     * @param $provider
80
     * @return \Illuminate\Http\RedirectResponse
81
     */
82
    public function handleProviderCallback($provider)
83
    {
84
        try {
85
            $user = $this->socialProvider->driver($provider)->user();
86
        } catch (Exception $e) {
0 ignored issues
show
The class Acacha\LaravelSocial\Http\Controllers\Exception does not exist. Did you forget a USE statement, or did you not list all dependencies?

Scrutinizer analyzes your composer.json/composer.lock file if available to determine the classes, and functions that are defined by your dependencies.

It seems like the listed class was neither found in your dependencies, nor was it found in the analyzed files in your repository. If you are using some other form of dependency management, you might want to disable this analysis.

Loading history...
87
            return Redirect::to('auth/' . $provider);
88
        }
89
90
        $this->auth->login($this->users->provider($provider)->findOrCreateUser($user), true);
0 ignored issues
show
The method login() does not seem to exist on object<Illuminate\Contracts\Auth\Factory>.

This check looks for calls to methods that do not seem to exist on a given type. It looks for the method on the type itself as well as in inherited classes or implemented interfaces.

This is most likely a typographical error or the method has been renamed.

Loading history...
91
92
        return redirect()->intended($this->redirectPath());
93
    }
94
}
95