Title: ====== MailOrderWorks v5.907 - Multiple Web Vulnerabilities Date: ===== 2013-01-02 References: =========== http://www.vulnerability-lab.com/get_content.php?id=798 VL-ID: ===== 796 Common Vulnerability Scoring System: ==================================== 4.5 Introduction: ============= Mail order management and stock control is easy with MailOrderWorks. MailOrderWorks (aka MOW) is an easy to use mail order software and stock control system that supports multiple users, but is also ideal for single person companies too. Our software allows you and your staff to access the same information, at the same time, from anywhere - even if you`re not in the same office or building. It`s affordable, easy to use, allows integration and is easily expandable for more users. It`s free to try too. (Copy of the Vendor Homepage: http://www.mailorderworks.co.uk/index.php ) Abstract: ========= The Vulnerability-Laboratory Research Team discovered multiple web vulnerabilities in MailOrderWorks v5.907, Mail order management application. Report-Timeline: ================ 2012-12-26: Public Disclosure Status: ======== Published Affected Products: ================== 2Dmedia Product: MailOrderWorks 5.907 Exploitation-Technique: ======================= Remote Severity: ========= Medium Details: ======== Multiple persistent web vulnerabilities are detected in the MailOrderWorks v5.907, Mail order management application. The vulnerability allows an attacker to inject own malicious script code in the vulnerable modules on application side (persistent). The vulnerabilities mainly exist in the create document/print module. The module doesn`t validate the file context when processing to create. For example, if we are creating a products summary, the print module(vulnerable) doesn`t check the products titles, and creates the document with the injected malicious code inside. 1.1 The first vulnerability is located in the `dispatch order` module. The attacker can create an order by injecting the malicious code in the vulnerable customer parameters which are firstname, lastname, custom A1 and custom A2. For the malicious code to get executed, the target user should go to `dispatch order` module `Open Batch screen` and then click `start`. The output file executes the malicious script code while creating the malicious order via add. 1.2 The second vulnerability is located in the `reports and exports` module. The attacker can create an order injecting the vulnerable parameters in it. The malicious code will be executed when the user choose the orders and create a report about them. The vulnerability also can be executed from creating a report about the products. The attacker can create a product with injecting malicious code in the vulnerable parameters which are SKU, Title and Group. When the user create a report about the products, the malicious code will be executed out of the context from the report file 1.3 The persistent input validation vulnerability is located in the `Create/View issue` in the show/add orders modules. The attacker can inject malicious codes in different vulnerable parameters which are Reason/fault, Resolution, Issue Notes and Order notes. Whenever the user clicks on `print issue document` a file will be generated and it includes the malicious codes where it gets executed. 1.4 The final persistent cross-site scripting vulnerability is ver critical because it gets injected in every file that is being generated from the MailOrderWorld(MOW). The vulnerability is located in the settings of the application where the attacker can inject a malicious code inside the company profiles in the vulnerable fields which are, Company Name and Address. Whenever a user generates any page, the malicious code will be executed because the fields: `company name` and `company address` are included in every page that is generated by MOW. The vulnerability can be exploited with privileged application user account and low or medium required user interaction. Successful exploitation of the vulnerability result in persistent/non-persistent session hijacking, persistent/non-persistent phishing, external redirect, external malware loads and persistent/non-persistent vulnerable module context manipulation. Vulnerable Service(s): [+] MailOrderWorks (5.907) Vulnerable Section(s): [+] New Order [+] Add new Product [+] View Orders [+] Settings Vulnerable Module(s): [+] Customer [+] Add new Product [+] View Orders => Done => Create/View Issue [+] Company Settings Vulnerable Parameter(s): [+] [Name] - [Mobile/Work] - [Custom A1] - [Custom A2] - [Custom B] - [Email] [+] [SKU] - [Title] - [Group] [+] [Reason/fault] - [Resolution] - [Issue Notes] - [Order notes] [+] [Company name] - [Address] - [Document Title] - [Details/Message] Affected Module(s): [+] dispatch order > Open batch screen > Start [+] Reports and Exports > [Products] - [Dispatch] [+] View Orders > Done > Create/View Issue > Print issue Document [+] Any document Generated by MOW Proof of Concept: ================= The persistent input validation web vulnerabilities can be exploited by remote attackers with low or medium required user interaction and low privileged application user account. For demonstration or reproduce ... #1 Vulnerable Module(s): New Order => [Name] - [Mobile/Work] - [Custom A1] - [Custom A2] - [Custom B] - [Email] Affected Module(s): dispatch order => open batch screen => start Code Review:

Sales Invoice

Invoice No.
1004
Order Date
12/24/2012
Custom B1
[PERSISTENT INJECTED SCRIPT CODE!]
Custom B2
[PERSISTENT INJECTED SCRIPT CODE!]
vlabs
Example Unit
Works Business Park
Mail Order Road
County
AB1 2BC
Phone: (edit in settings)
Email: (edit in settings)
Web: (edit in settings)
Company No. (edit in settings), VAT Reg No. (edit in settings)

Deliver To

Mr [PERSISTENT INJECTED SCRIPT CODE!]

Invoice To

Mr"><[PERSISTENT INJECTED SCRIPT CODE!]")>
Customer
[PERSISTENT INJECTED SCRIPT CODE!]
Account
568-3671
Custom A1
[PERSISTENT INJECTED SCRIPT CODE!]
Custom A2
[PERSISTENT INJECTED SCRIPT CODE!]
SKU Description
Qty
Rate
Unit Price
Line Total
#2 Vulnerable Module(s): Add new Product => [SKU] - [Title] - [Group] Affected Module(s): Reports and Exports => [Products] - [Dispatch] Code Review: SKU Title Spec Group Retail Price Available In Stock Pending Allocated Low Level Cost Supplier Sold Last Sold Stock First Arrival [PERSISTENT INJECTED SCRIPT CODE!]'=20 src=3D"res://ieframe.dll/dnserrordiagoff_webOC.htm"> [PERSISTENT INJECTED SCRIPT CODE!]'=20 src=3D"res://ieframe.dll/dnserrordiagoff_webOC.htm"> [PERSISTENT INJECTED SCRIPT CODE!]'=20 src=3D"res://ieframe.dll/dnserrordiagoff_webOC.htm"> [PERSISTENT INJECTED SCRIPT CODE!]'=20 src=3D"res://ieframe.dll/dnserrordiagoff_webOC.htm"> =A31.00 10 10 0 0 0 =A312.00 12/24/2012 BBA123G Angled Building Block #3 Vulnerable Module(s): View Orders => [Reason/fault] - [Resolution] - [Issue Notes] - [Order notes] Affected Module(s): Reports and Exports => View Orders => Done => Create/View Issue => print issue Document Code Review:

Fault Description

Created: 12/25/2012

= [PERSISTENT INJECTED SCRIPT CODE!]

Resolution

Resolved:

= [PERSISTENT INJECTED SCRIPT CODE!] Fault = Report Notes=20 [PERSISTENT INJECTED SCRIPT CODE!] Order Notes = [PERSISTENT INJECTED SCRIPT CODE!] ... Vulnerable Module(s): Settings => [Company name] - [Address] - [Document Title] - [Details/Message] Affected Module(s): all generated files by MOW Code Review: From: Subject: [PERSISTENT INJECTED SCRIPT CODE!](MailOrderWorks) Date: Tue, 25 Dec 2012 11:59:57 -0800 MIME-Version: 1.0 Content-Type: multipart/related; type="text/html"; boundary="----=_NextPart_000_0000_01CDE297.5C26ACF0" X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 class=3Dstyle20>



[PERSISTENT INJECTED SCRIPT CODE!]
[PERSISTENT INJECTED SCRIPT CODE!]

Risk: ===== The security risk of the persistent input validation web vulnerabilities are estimated as medium(+). Credits: ======== Vulnerability Laboratory [Research Team] - Ibrahim El-Sayed (the_storm) [storm@vulnerability-lab.com] [iel-sayed.blogspot.com] Disclaimer: =========== The information provided in this advisory is provided as it is without any warranty. Vulnerability-Lab disclaims all warranties, either expressed or implied, including the warranties of merchantability and capability for a particular purpose. Vulnerability- Lab or its suppliers are not liable in any case of damage, including direct, indirect, incidental, consequential loss of business profits or special damages, even if Vulnerability-Lab or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply. We do not approve or encourage anybody to break any vendor licenses, policies, deface websites, hack into databases or trade with fraud/stolen material. Domains: www.vulnerability-lab.com - www.vuln-lab.com - www.vulnerability-lab.com/register Contact: admin@vulnerability-lab.com - support@vulnerability-lab.com - research@vulnerability-lab.com Section: video.vulnerability-lab.com - forum.vulnerability-lab.com - news.vulnerability-lab.com Social: twitter.com/#!/vuln_lab - facebook.com/VulnerabilityLab - youtube.com/user/vulnerability0lab Feeds: vulnerability-lab.com/rss/rss.php - vulnerability-lab.com/rss/rss_upcoming.php - vulnerability-lab.com/rss/rss_news.php Any modified copy or reproduction, including partially usages, of this file requires authorization from Vulnerability Laboratory. Permission to electronically redistribute this alert in its unmodified form is granted. All other rights, including the use of other media, are reserved by Vulnerability-Lab Research Team or its suppliers. All pictures, texts, advisories, sourcecode, videos and other information on this website is trademark of vulnerability-lab team & the specific authors or managers. To record, list (feed), modify, use or edit our material contact (admin@vulnerability-lab.com or support@vulnerability-lab.com) to get a permission. Copyright © 2013 | Vulnerability Laboratory -- VULNERABILITY RESEARCH LABORATORY LABORATORY RESEARCH TEAM CONTACT: research@vulnerability-lab.com