{"vuid":"VU#528212","idnumber":"528212","name":"Lomtec ActiveWeb Professional 3.0 CMS allows arbitrary file upload and execution","keywords":["Lomtec","ActiveWeb Professional 3.0 CMS"],"overview":"Lomtec ActiveWeb Professional 3.0 web content management server allows unauthenticated users to upload arbitrary files.","clean_desc":"According to Lomtec's website: \"Lomtec ActiveWeb offers an ideal solution for the creation, maintenance and administration of a Web site and its content.\" Lomtec ActiveWeb Professional 3.0 web content management server, running on ColdFusion, allows unauthenticated users to upload arbitrary files. By accessing the \"getImagefile\" section of the EasyEdit module, a remote attacker could upload an executable server-side script (e.g., an .asp shell on a Microsoft Internet Information Server platform) and execute arbitrary commands with the privileges of the web content management server.","impact":"By uploading a file that can be executed by the web server (e.g., an .asp shell), a remote, authenticated attacker may be able to execute arbitrary code with the privileges of the web content management server.","resolution":"We are currently unaware of a practical solution to this problem.","workarounds":"Restrict Access Limit network access to hosts that require connections to the web content management server. Do not allow access to the web content management server from untrusted networks such as the internet. Filter URLs Using a reverse HTTP proxy, web server URL filtering, or similar technology, it may be possible to restrict the names and extensions of files that can be uploaded to the web content management server. Modify Web Server Permissions It may be possible to modify web content management server permissions to prevent file uploads. This may impact web content management server functionality.","sysaffected":"","thanks":"Thanks to StenoPlasma at ExploitDevelopment for reporting this vulnerability.","author":"This document was written by Michael Orlando.","public":["h","t","t","p",":","/","/","w","w","w",".","e","x","p","l","o","i","t","d","e","v","e","l","o","p","m","e","n","t",".","c","o","m","/","V","u","l","n","e","r","a","b","i","l","i","t","i","e","s","/","2","0","1","0","-","W","E","B","-","0","0","2",".","h","t","m","l"],"cveids":[""],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2010-12-02T19:41:54Z","publicdate":"2011-01-28T00:00:00Z","datefirstpublished":"2011-01-25T13:42:24Z","dateupdated":"2011-01-25T13:42:24Z","revision":14,"vrda_d1_directreport":"1","vrda_d1_population":"2","vrda_d1_impact":"3","cam_widelyknown":"1","cam_exploitation":"0","cam_internetinfrastructure":"3","cam_population":"14","cam_impact":"15","cam_easeofexploitation":"17","cam_attackeraccessrequired":"20","cam_scorecurrent":"5.355","cam_scorecurrentwidelyknown":"30.79125","cam_scorecurrentwidelyknownexploited":"57.56625","ipprotocol":"","cvss_accessvector":"","cvss_accesscomplexity":"","cvss_authentication":null,"cvss_confidentialityimpact":"","cvss_integrityimpact":"","cvss_availabilityimpact":"","cvss_exploitablity":null,"cvss_remediationlevel":"","cvss_reportconfidence":"","cvss_collateraldamagepotential":"","cvss_targetdistribution":"","cvss_securityrequirementscr":"","cvss_securityrequirementsir":"","cvss_securityrequirementsar":"","cvss_basescore":"","cvss_basevector":"","cvss_temporalscore":"","cvss_environmentalscore":"","cvss_environmentalvector":"","metric":5.355,"vulnote":null}