what you don't know can hurt you
Home Files News &[SERVICES_TAB]About Contact Add New

UDID 1.0 Script Injection

UDID 1.0 Script Injection
Posted Sep 22, 2015
Authored by Benjamin Kunz Mejri, Vulnerability Laboratory | Site vulnerability-lab.com

UDID version 1.0 suffers from a persistent mail encoding vulnerability that allows for script injection.

tags | exploit
SHA-256 | bceca9f113e5c423a0b3c8001f9d90a113dcbd637c3da7bc1db7f038a0018c2a

UDID 1.0 Script Injection

Change Mirror Download
Document Title:
UDID v1.0 iOS - Persistent Mail Encode Vulnerability

References (Source):

Release Date:

Vulnerability Laboratory ID (VL-ID):

Common Vulnerability Scoring System:

Product & Service Introduction:
Here is the easiest way to get your device information such as UDID, Device Name, OS Version and many more,
in just one click. You can also share your device information with any one.

(Copy of the Vendor Homepage: https://itunes.apple.com/de/app/my-device-udid/id504520659 )

Abstract Advisory Information:
The Vulnerability Laboratory Research Team discovered application-side validation vulnerability in the official UDID v1.0 iOS mobile web-application.

Vulnerability Disclosure Timeline:
2015-09-22: Public Disclosure (Vulnerability Laboratory)

Discovery Status:

Affected Product(s):
Hiteshi Technologies
Product: UDID+ - iOS Mobile Web Application 1.0

Exploitation Technique:

Severity Level:

Technical Details & Description:
An application-side input validation web vulnerability has been discovered in the official UDID v1.0 iOS mobile web-application.
The security web vulnerability allows to inject malicious script codes to the application-side of the vulnerable iOS mobile app.

The vulnerability is located in the `Send UDID via Email` encoding. The application encodes the input of the device cell name with
wrong conditions. Thus results in an application-side script code execution issue in the Send UDID via Email module. The attackers
changes by restricted physical device access the device cell name to compromise the application output in the Send UDID via Email module.

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 privilege ios device account with restricted access and no user interaction.
Successful exploitation of the vulnerabilities results in persistent phishing mails, session hijacking, persistent external redirect to malicious
sources and application-side manipulation of affected or connected module context.

Vulnerable Module(s)
[+] Send UDID via Email

Vulnerable Parameter(s)
[+] device cell name (cid)

Affected Module(s)
[+] UDID Device Information (Mail)

Proof of Concept (PoC):
The application-side mail encoding web vulnerability can be exploited by local attackers with restricted physical device access without 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. Change the cid of the ios device via settings to a script code payload (test)
2. Open the vulnerable application
3. Click the Send UDID via Email button
4. Push the email button
5. The function includes the device values with wrong encoding to the email
6. Successful reproduce of the vulnerability!

PoC: UDID.html
<div><u><b>DEVICE INFORMATION</b></u><br><br><b>UDID:</b> FFFFFFFFE9BBB73F956742C78479FE9A6F3F1DF1
<br><b>Device Name:</b> bkm337>"<img src"x"="" src="cid:">%20<iframe src="a">%20<iframe><br /><b>
System Name:</b> iPhone OS<br /><b>System Version:</b> 8.3<br /><b>
Platform:</b> iPad 2<br /><b>Model:</b> iPad<br /><b>
Language:</b> de<br /><b>Battery State:</b>
UnPlugged<br /><b>Local IP:</b><br /><b>
Battery Level:</b> 65 %<br /><br />This email was sent using UDID<br /></iframe>

Security Risk:
The security risk of the persistent validation web vulnerability in the udid device information app is estimated as medium. (CVSS 3.6)

Credits & Authors:
Vulnerability Laboratory [Research Team] - Benjamin Kunz Mejri (bkm@evolution-sec.com) [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@vulnerability-lab.com - research@vulnerability-lab.com - admin@evolution-sec.com
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@vulnerability-lab.com or research@vulnerability-lab.com) to get a permission.

Copyright © 2015 | Vulnerability Laboratory - [Evolution Security GmbH]™

SERVICE: www.vulnerability-lab.com
CONTACT: research@vulnerability-lab.com
PGP KEY: http://www.vulnerability-lab.com/keys/admin@vulnerability-lab.com%280x198E9928%29.txt

Login or Register to add favorites

File Archive:

March 2023

  • Su
  • Mo
  • Tu
  • We
  • Th
  • Fr
  • Sa
  • 1
    Mar 1st
    16 Files
  • 2
    Mar 2nd
    13 Files
  • 3
    Mar 3rd
    15 Files
  • 4
    Mar 4th
    0 Files
  • 5
    Mar 5th
    0 Files
  • 6
    Mar 6th
    16 Files
  • 7
    Mar 7th
    31 Files
  • 8
    Mar 8th
    16 Files
  • 9
    Mar 9th
    13 Files
  • 10
    Mar 10th
    9 Files
  • 11
    Mar 11th
    0 Files
  • 12
    Mar 12th
    0 Files
  • 13
    Mar 13th
    10 Files
  • 14
    Mar 14th
    6 Files
  • 15
    Mar 15th
    17 Files
  • 16
    Mar 16th
    22 Files
  • 17
    Mar 17th
    13 Files
  • 18
    Mar 18th
    0 Files
  • 19
    Mar 19th
    0 Files
  • 20
    Mar 20th
    16 Files
  • 21
    Mar 21st
    13 Files
  • 22
    Mar 22nd
    5 Files
  • 23
    Mar 23rd
    6 Files
  • 24
    Mar 24th
    47 Files
  • 25
    Mar 25th
    0 Files
  • 26
    Mar 26th
    0 Files
  • 27
    Mar 27th
    0 Files
  • 28
    Mar 28th
    0 Files
  • 29
    Mar 29th
    0 Files
  • 30
    Mar 30th
    0 Files
  • 31
    Mar 31st
    0 Files

Top Authors In Last 30 Days

File Tags


packet storm

© 2022 Packet Storm. All rights reserved.

Security Services
Hosting By