[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
SevDesk v1.1 iOS - Persistent Dashboard Vulnerability
SevDesk v1.1 iOS - Persistent Dashboard Vulnerability
Vulnerability Laboratory ID (VL-ID):
Common Vulnerability Scoring System:
Product & Service Introduction:
Official app for mobile use of sevDesk. A product of SEVENIT GmbH.
256bit SSL encryption
TÜV certified data center
No hidden costs
No minimum contract term
Runs in any browser
No installation required on the PC
Easy to use
Reduced to the essentials
Automated, where it is only possible
(Copy of the Vendor Homepage: https://sevdesk.de/ )
Abstract Advisory Information:
The Vulnerability Laboratory Research Team discovered multiple vulnerabilities in the official SEVENIT GmbH SevDesk mobile application (api).
Vulnerability Disclosure Timeline:
2014-09-01: Researcher Notification & Coordination (Benjamin Kunz Mejri)
2014-09-02: Vendor Notification (SevDesk Developer Team)
2015-04-23: Public Disclosure (Vulnerability Laboratory)
Product: SevDesk - iOS Mobile Web Application (API) 1.1
Technical Details & Description:
A persistent input validation web vulnerability has been discovered in the official SEVENIT Software GmbH sevDesk v1.1 iOS mobile web-application (api).
The vulnerability allows remote attackers or low privileged user account to inject own malicious script codes to the application-side of the vulnerable
web-application module or service.
The security vulnerability is located in the `firstname` values of the main sevDesk `Dasboard` application module & api. Remote attackers are able to inject
own script codes to the mobile dashboard through the api by manipulation of the registration information in the client.
The execution of the script code occurs after the inject on the application-side in the main mobile dashboard status list. If the test user account apply for
any changes in the account profile the activity becomes visible. In the context were the information and details becomes visible is the location were the
execution of the persistent injected script code takes place. The attack vector is persistent and the request method to inject the code is POST.
The security risk of the persistent script code inject web vulnerability is estimated as medium with a cvss (common vulnerability scoring system) count of 4.2.
Exploitation of the persistent input validation web vulnerability requires a low privileged sevdesk user account with restricted access and low user interaction.
Successful exploitation of the vulnerability results in session hijacking, persistent phishing, persistent external redirects to malicious source and persistent
manipulation of affected or connected application modules (api).
[+] sevDesk v1.1 iOS
[+] Registration to SevDesk
[+] firstname (display name)
[+] Dasboard Index Status List
Proof of Concept (PoC):
The persistent input validation web vulnerability can be exploited by remote attackers with low privileged application user account and low user interaction.
For security demonstration or to reproduce the security vulnerability follow the provided information and steps below to continue.
1. Install the application to your iOS device (ipad iphone)
2. Register an new account
3. Include as name value your own malicious script code payload
4. Save the settings and open the Dasboard status listing
Note: After the save the context gets discplayed by the mobile app api through the web database
5. The script code execution occurs in the main status messages
6. Successful reproduce of the security vulnerability in the mobile iOS application!
Solution - Fix & Patch:
The issue can be patched by a secure parse and encode of the user credentials on registration through the mobile application api.
Restrict the user input to register and parse also the status listing in the main dasboard which becomes visible after the malicious changes.
The security risk of the persistent mobile web vulnerability in the api is estimated as medium. (CVSS 4.2)
Credits & Authors:
Vulnerability Laboratory [Research Team] - Benjamin Kunz Mejri (bkm@xxxxxxxxxxxxxxxxx) [www.vulnerability-lab.com]
Disclaimer & Information:
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.evolution-sec.com
Contact: admin@xxxxxxxxxxxxxxxxxxxxx - research@xxxxxxxxxxxxxxxxxxxxx - admin@xxxxxxxxxxxxxxxxx
Section: magazine.vulnerability-db.com - vulnerability-lab.com/contact.php - evolution-sec.com/contact
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
Programs: vulnerability-lab.com/submit.php - vulnerability-lab.com/list-of-bug-bounty-programs.php - vulnerability-lab.com/register/
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, source code, 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@xxxxxxxxxxxxxxxxxxxxx or research@xxxxxxxxxxxxxxxxxxxxx) to get a permission.
Copyright © 2015 | Vulnerability Laboratory - [Evolution Security GmbH]™
VULNERABILITY LABORATORY - RESEARCH TEAM
PGP KEY: http://www.vulnerability-lab.com/keys/admin@xxxxxxxxxxxxxxxxxxxxx%280x198E9928%29.txt