Apple WGT Dictionnaire 1.3 Script Code Injection
Apple WGT Dictionnaire 1.3 - Script Code Inject Vulnerability
Common Vulnerability Scoring System:
The Vulnerability Laboratory Research Team discovered a script code inject vulnerability in Apples (MacOSx) Widget Dictionnaire v1.3 software.
2012-11-27: Public Disclosure
A persistent script code inject vulnerability is detected in the Dictionnaire, Dictionary of the French language based on TLFi (in French), Software.
The vulnerability allows a local attacker execute malicious codes to compromise the connected client system in the lan. The command execution
vulnerability is located in the search field of the Dictionnaire module. The malicious injected script code will be directly executed out of
the result field. Successful exploitation of the vulnerability results in system compromise via script code injections, persistent software
context manipulation, external malware loads or malicious external redirects.
Vulnerable Software Module(s):
[+] Search Box
Vulnerable Software Parameter(s):
[+] Search Field
Proof of Concept:
The software validation vulnerability can be exploited by local attackers with required user interaction and privileged local system account.
For demonstration or reproduce ...
PoC: Script Code Inject
"<iframe src=vuln-lab.com onload=alert("VLab") <>
The vulnerability can be patched by parsing the search string input field and result output (listing) web context.
The security risk of the remote command execution vulnerability is estimated as high(+).
Vulnerability Laboratory [Research Team] - Ibrahim El-Sayed (the_storm) [email@example.com] [iel-sayed.blogspot.com]
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: firstname.lastname@example.org - email@example.com - firstname.lastname@example.org
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 (email@example.com or firstname.lastname@example.org) to get a permission.
Copyright © 2012 | Vulnerability Laboratory
VULNERABILITY RESEARCH LABORATORY
LABORATORY RESEARCH TEAM