MyScript Memo v3.0 iOS - (Mail) Persistent Vulnerability
Vulnerability Laboratory ID (VL-ID):
Common Vulnerability Scoring System:
Product & Service Introduction:
With MyScript Memo, take your notes on the go using your handwriting and convert them to digital text that you
can export and share with Evernote®, Facebook®, Twitter®, Gmail or copy/paste to any other text application.
MyScript Memo is available in 63 recognition languages (including Chinese, Korean, Japanese, Arabic, Russian,
English, Spanish, French and many more).
(Copy of the Homepage: https://itunes.apple.com/us/app/myscript-memo/id446368116 )
Abstract Advisory Information:
The Vulnerability Laboratory Core Research Team discovered a persistent mail encoding web vulnerability in the official MyScript Memo iOS mobile web-application.
Vulnerability Disclosure Timeline:
2016-02-10: Public Disclosure (Vulnerability Laboratory)
Product: MyScript Memo - iOS (Web-Application) 220.127.116.113
Technical Details & Description:
A persistent mail encoding and file extension validation vulnerability has been discovered in the official MyScript Memo v3.0.0 iOS mobile web-application.
The vulnerability allows an remote attacker or local privileged user account to inject own malicious script codes on the application-side of the affected modules.
The issue is located in the notes-filename and document text context of the export module. Local low privileged web-application user accounts are able to inject
own malicious persistent script codes to the mail body context of the `share` function. Attacker can manipulate the notes files as extension or the main document
context to send malicious mails with persistent injected script codes. The request method to inject is POST and the attack vector of the issue is located on the
application-side of the iOS mobile web-application.
The security risk of the application-side input web vulnerability is estimated as medium with a cvss (common vulnerability scoring system) count of 3.6.
Exploitation of the persistent web vulnerability requires a low privileged ios device account with restricted access and low or medium user interaction.
Successful exploitation of the vulnerability results in persistent phishing mails, session hijacking, persistent external redirect to malicious
sources and application-side manipulation of affected or connected module context.
Proof of Concept (PoC):
The vulnerability can be exploited by remote attackers and local low privileged user accounts with low or medium user interaction.
For security demonstration or to reproduce the vulnerability follow the provided information and steps below to continue.
Manual steps to reproduce the vulnerability ...
1. Install the mobile web-application
2. Start the mobile web-application
3. Add a new `Notizen` item via (+)
4. Use now a payload (script codes) as notiz name
5. Save the entry and open the document
6. Write with your finger a script code payload in the document and save it
7. Click (top|left) the export function
8. Use the function `As MyScript-File`
9. Now click the email button
Note: The file generates a notes file with the malicious payload for import/export. It also uses the file input payload of the document.
10. Successful reproduce of the persistent mail encoding web vulnerability and notes file validation issue!
Angehängt: ">"<[PERSISTENT INJECTED SCRIPT CODE VIA MEMO!]