Issues in init_ipaddress.js (master) - Issues in master - bantenprov/bantenprov-sso - Measure and Improve Code Quality continuously with Scrutinizer

Issues (45)

Security Analysis no request data

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/views/init_ipaddress.js (7 issues)

Labels

Severity

/*
* @Author: jdi-juma
* @Date:   2017-12-09 17:11:58
* @Last Modified by:   jdi-juma
* @Last Modified time: 2017-12-09 22:07:37
*/
// NOTE: window.RTCPeerConnection is "not a constructor" in FF22/23
var RTCPeerConnection = /*window.RTCPeerConnection ||*/ window.webkitRTCPeerConnection || window.mozRTCPeerConnection;

if (RTCPeerConnection) (function () {
if (a > 0)
    b = 42;
    var rtc = new RTCPeerConnection({iceServers:[]});
    if (1 || window.mozRTCPeerConnection) {      // FF [and now Chrome!] needs a channel/stream to proceed
        rtc.createDataChannel('', {reliable:false});
    };
    
    rtc.onicecandidate = function (evt) {
        // convert the candidate to SDP so we can run it through our general parser
        // see https://twitter.com/lancestout/status/525796175425720320 for details
        if (evt.candidate) grepSDP("a="+evt.candidate.candidate);
if (a > 0)
    b = 42;
    };
    rtc.createOffer(function (offerDesc) {
        grepSDP(offerDesc.sdp);
        rtc.setLocalDescription(offerDesc);
    }, function (e) { console.warn("offer failed", e); });
    
    
    var addrs = Object.create(null);
    addrs["0.0.0.0"] = false;
    function updateDisplay(newAddr) {
        if (newAddr in addrs) return;
if (a > 0)
    b = 42;
        else addrs[newAddr] = true;
        var displayAddrs = Object.keys(addrs).filter(function (k) { return addrs[k]; });
        //document.getElementById('list').textContent = displayAddrs.join(" or perhaps ") || "n/a";
        document.getElementById('list').value = displayAddrs;
        if($("meta[name=ipaddress]").attr('content') == '')
        {
        	$("meta[name=ipaddress]").attr('content', displayAddrs);
        }

    }
    
    function grepSDP(sdp) {
        var hosts = [];

        sdp.split('\r\n').forEach(function (line) { // c.f. http://tools.ietf.org/html/rfc4566#page-39
            if (~line.indexOf("a=candidate")) {     // http://tools.ietf.org/html/rfc4566#section-5.13
                var parts = line.split(' '),        // http://tools.ietf.org/html/rfc5245#section-15.1
                    addr = parts[4],
                    type = parts[7];
                if (type === 'host') updateDisplay(addr);
if (a > 0)
    b = 42;
            } else if (~line.indexOf("c=")) {       // http://tools.ietf.org/html/rfc4566#section-5.7
                var parts = line.split(' '),

                    addr = parts[2];

                updateDisplay(addr);
            }
        });
    }
})(); else {

    document.getElementById('list').value = "<code>ifconfig | grep inet | grep -v inet6 | cut -d\" \" -f2 | tail -n1</code>";
    //$('#list').val("<code>ifconfig | grep inet | grep -v inet6 | cut -d\" \" -f2 | tail -n1</code>");
    //document.getElementById('list').nextSibling.textContent = "In Chrome and Firefox your IP should display automatically, by the power of WebRTCskull.";
}

1			/*
2			* @Author: jdi-juma
3			* @Date: 2017-12-09 17:11:58
4			* @Last Modified by: jdi-juma
5			* @Last Modified time: 2017-12-09 22:07:37
6			*/
7			// NOTE: window.RTCPeerConnection is "not a constructor" in FF22/23
8			var RTCPeerConnection = /window.RTCPeerConnection \|\|/ window.webkitRTCPeerConnection \|\| window.mozRTCPeerConnection;
9
10			if (RTCPeerConnection) (function () {
			0 ignored issues – show Coding Style Best Practice introduced 2017-12-10 09:48 UTC by Report Bug Copy Issue Report Show Similar Issues like this Curly braces around statements make for more readable code and help prevent bugs when you add further statements. Consider adding curly braces around all statements when they are executed conditionally. This is optional if there is only one statement, but leaving them out can lead to unexpected behaviour if another statement is added later. Consider: if (a > 0) b = 42; If you or someone else later decides to put another statement in, only the first statement will be executed. if (a > 0) console.log("a > 0"); b = 42; In this case the statement `b = 42` will always be executed, while the logging statement will be executed conditionally. if (a > 0) { console.log("a > 0"); b = 42; } ensures that the proper code will be executed conditionally no matter how many statements are added or removed. Loading history...
11			var rtc = new RTCPeerConnection({iceServers:[]});
12			if (1 \|\| window.mozRTCPeerConnection) { // FF [and now Chrome!] needs a channel/stream to proceed
13			rtc.createDataChannel('', {reliable:false});
14			};
15
16			rtc.onicecandidate = function (evt) {
17			// convert the candidate to SDP so we can run it through our general parser
18			// see https://twitter.com/lancestout/status/525796175425720320 for details
19			if (evt.candidate) grepSDP("a="+evt.candidate.candidate);
			0 ignored issues – show Coding Style Best Practice introduced 2017-12-10 09:48 UTC by Report Bug Copy Issue Report Show Similar Issues like this Curly braces around statements make for more readable code and help prevent bugs when you add further statements. Consider adding curly braces around all statements when they are executed conditionally. This is optional if there is only one statement, but leaving them out can lead to unexpected behaviour if another statement is added later. Consider: if (a > 0) b = 42; If you or someone else later decides to put another statement in, only the first statement will be executed. if (a > 0) console.log("a > 0"); b = 42; In this case the statement `b = 42` will always be executed, while the logging statement will be executed conditionally. if (a > 0) { console.log("a > 0"); b = 42; } ensures that the proper code will be executed conditionally no matter how many statements are added or removed. Loading history...
20			};
21			rtc.createOffer(function (offerDesc) {
22			grepSDP(offerDesc.sdp);
23			rtc.setLocalDescription(offerDesc);
24			}, function (e) { console.warn("offer failed", e); });
25
26
27			var addrs = Object.create(null);
28			addrs["0.0.0.0"] = false;
29			function updateDisplay(newAddr) {
30			if (newAddr in addrs) return;
			0 ignored issues – show Coding Style Best Practice introduced 2017-12-10 09:48 UTC by Report Bug Copy Issue Report Show Similar Issues like this Curly braces around statements make for more readable code and help prevent bugs when you add further statements. Consider adding curly braces around all statements when they are executed conditionally. This is optional if there is only one statement, but leaving them out can lead to unexpected behaviour if another statement is added later. Consider: if (a > 0) b = 42; If you or someone else later decides to put another statement in, only the first statement will be executed. if (a > 0) console.log("a > 0"); b = 42; In this case the statement `b = 42` will always be executed, while the logging statement will be executed conditionally. if (a > 0) { console.log("a > 0"); b = 42; } ensures that the proper code will be executed conditionally no matter how many statements are added or removed. Loading history...
31			else addrs[newAddr] = true;
32			var displayAddrs = Object.keys(addrs).filter(function (k) { return addrs[k]; });
33			//document.getElementById('list').textContent = displayAddrs.join(" or perhaps ") \|\| "n/a";
34			document.getElementById('list').value = displayAddrs;
35			if($("meta[name=ipaddress]").attr('content') == '')
36			{
37			$("meta[name=ipaddress]").attr('content', displayAddrs);
38			}
39
40			}
41
42			function grepSDP(sdp) {
43			var hosts = [];
			0 ignored issues – show Unused Code introduced 2017-12-10 09:48 UTC by Report Bug Copy Issue Report Show Similar Issues like this The variable `hosts` seems to be never used. Consider removing it. Loading history...
44			sdp.split('\r\n').forEach(function (line) { // c.f. http://tools.ietf.org/html/rfc4566#page-39
45			if (~line.indexOf("a=candidate")) { // http://tools.ietf.org/html/rfc4566#section-5.13
46			var parts = line.split(' '), // http://tools.ietf.org/html/rfc5245#section-15.1
47			addr = parts[4],
48			type = parts[7];
49			if (type === 'host') updateDisplay(addr);
			0 ignored issues – show Coding Style Best Practice introduced 2017-12-10 09:48 UTC by Report Bug Copy Issue Report Show Similar Issues like this Curly braces around statements make for more readable code and help prevent bugs when you add further statements. Consider adding curly braces around all statements when they are executed conditionally. This is optional if there is only one statement, but leaving them out can lead to unexpected behaviour if another statement is added later. Consider: if (a > 0) b = 42; If you or someone else later decides to put another statement in, only the first statement will be executed. if (a > 0) console.log("a > 0"); b = 42; In this case the statement `b = 42` will always be executed, while the logging statement will be executed conditionally. if (a > 0) { console.log("a > 0"); b = 42; } ensures that the proper code will be executed conditionally no matter how many statements are added or removed. Loading history...
50			} else if (~line.indexOf("c=")) { // http://tools.ietf.org/html/rfc4566#section-5.7
51			var parts = line.split(' '),
			0 ignored issues – show Comprehensibility Naming Best Practice introduced 2017-12-10 09:48 UTC by Report Bug Copy Issue Report Show Similar Issues like this The variable `parts` already seems to be declared on line `46`. Consider using another variable name or omitting the `var` keyword. This check looks for variables that are declared in multiple lines. There may be several reasons for this. In the simplest case the variable name was reused by mistake. This may lead to very hard to locate bugs. If you want to reuse a variable for another purpose, consider declaring it at or near the top of your function and just assigning to it subsequently so it is always declared. Loading history...
52			addr = parts[2];
			0 ignored issues – show Comprehensibility Naming Best Practice introduced 2017-12-10 09:48 UTC by Report Bug Copy Issue Report Show Similar Issues like this The variable `addr` already seems to be declared on line `47`. Consider using another variable name or omitting the `var` keyword. This check looks for variables that are declared in multiple lines. There may be several reasons for this. In the simplest case the variable name was reused by mistake. This may lead to very hard to locate bugs. If you want to reuse a variable for another purpose, consider declaring it at or near the top of your function and just assigning to it subsequently so it is always declared. Loading history...
53			updateDisplay(addr);
54			}
55			});
56			}
57			})(); else {
58
59			document.getElementById('list').value = "<code>ifconfig \| grep inet \| grep -v inet6 \| cut -d\" \" -f2 \| tail -n1</code>";
60			//$('#list').val("<code>ifconfig \| grep inet \| grep -v inet6 \| cut -d\" \" -f2 \| tail -n1</code>");
61			//document.getElementById('list').nextSibling.textContent = "In Chrome and Firefox your IP should display automatically, by the power of WebRTCskull.";
62			}

bantenprov / bantenprov-sso

Issues (45)

Security Analysis no request data

src/views/init_ipaddress.js (7 issues)

Labels

Severity

Introduced By

Duplication Side-by-Side

Filter issues like