Binance 1.5.0 Insecure File Permission

2018.07.18
Credit: ZwX
Risk: Low
Local: Yes
Remote: No
CVE: N/A
CWE: N/A

Document Title: =============== Binance v1.5.0 - Insecure File Permission Vulnerability References (Source): ==================== https://www.vulnerability-lab.com/get_content.php?id=2135 Release Date: ============= 2018-07-17 Vulnerability Laboratory ID (VL-ID): ==================================== 2135 Common Vulnerability Scoring System: ==================================== 2.5 Vulnerability Class: ==================== Access Permission Weakness Current Estimated Price: ======================== 500 - 1.000 Abstract Advisory Information: ============================== An independent vulnerability laboratory researcher discovered an insecure file permission vulnerability in the Binance v1.5.0 software. Vulnerability Disclosure Timeline: ================================== 2018-07-15: Researcher Notification & Coordination (Security Researcher) 2018-07-17: Public Disclosure (Vulnerability Laboratory) Discovery Status: ================= Published Affected Product(s): ==================== Binance Product: Binance 1.5.0 Exploitation Technique: ======================= Local Severity Level: =============== Low Authentication Type: ==================== Full authentication (admin) - full privileges User Interaction: ================= Medium User Interaction Disclosure Type: ================ Independent Security Research Technical Details & Description: ================================ Insecure File Permissions vulnerability has been discovered in the official Binance v1.5.0 software. The vulnerability allows local attackers to exploit insecure permissions setup for a software or process to exploit by manipulation. The vulnerability exists due to insecure default permissions set on the Binance.exe, start.exe and unins000.exe There are no integrity checks or validation proof to ensure that the executable file is not modified during the runtime or after it. A local attacker could exploit the local vulnerability by replacing `Binance.exe` and `start.exe` or `unins000.exe` with a malicious executable file. The malicious file could execute or modify with the LocalSystem permissions to followup with successful exploitation. Proof of Concept (PoC): ======================= Binance for windows contains a vulnerability that could allow a local attacker to gain elevated privileges. For security demonstration or to reproduce the vulnerability follow the provided information and steps below. -- PoC Session Logs (Permissions) -- C:Binance>icacls binance.exe Binance.exe BUILTINAdministrateurs:(I)(F) <--- Full Access AUTORITE NTSysteme:(I)(F) BUILTINUtilisateurs:(I)(RX) AUTORITE NTUtilisateurs authentifies:(I)(M) <--- Modify Information: 1 files correctly processed; 0 files failed to process C:Binance>icacls start.exe start.exe BUILTINAdministrateurs:(I)(F) <--- Full Access AUTORITE NTSysteme:(I)(F) BUILTINUtilisateurs:(I)(RX) AUTORITE NTUtilisateurs authentifies:(I)(M) <--- Modify Information: 1 files correctly processed; 0 files failed to process C:Binance>icacls unins000.exe unins000.exe BUILTINAdministrateurs:(I)(F) <--- Full Access AUTORITE NTSysteme:(I)(F) BUILTINUtilisateurs:(I)(RX) AUTORITE NTUtilisateurs authentifies:(I)(M) <--- Modify Information: 1 files correctly processed; 0 files failed to process Solution - Fix & Patch: ======================= Include multiple integrity checks for the software files on startup and during the static runtime. Change the access permissions for the process of all three executables files (binance.exe, stat.exe & uninst00.exe). Security Risk: ============== The security risk of the insecure file permissions vulnerability and missing integrity check in the software core is estimated as low. Credits & Authors: ================== ZwX [Vulnerability Laboratory - Security Manager] - https://www.vulnerability-lab.com/show.php?user=ZwX 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 licenses, policies, deface websites, hack into databases or trade with stolen data. Domains: www.vulnerability-lab.com www.vuln-lab.com www.vulnerability-db.com Services: magazine.vulnerability-lab.com paste.vulnerability-db.com infosec.vulnerability-db.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 Programs: vulnerability-lab.com/submit.php vulnerability-lab.com/register.php vulnerability-lab.com/list-of-bug-bounty-programs.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, source code, videos and other information on this website is trademark of vulnerability-lab team & the specific authors or managers. To record, list, modify, use or edit our material contact (admin@ or research@) to get a ask permission. Copyright (c) 2018 | Vulnerability Laboratory - [Evolution Security GmbH]

References:

https://www.vulnerability-lab.com/get_content.php?id=2135


Vote for this issue:
50%
50%


 

Thanks for you vote!


 

Thanks for you comment!
Your message is in quarantine 48 hours.

Comment it here.


(*) - required fields.  
{{ x.nick }} | Date: {{ x.ux * 1000 | date:'yyyy-MM-dd' }} {{ x.ux * 1000 | date:'HH:mm' }} CET+1
{{ x.comment }}

Copyright 2018, cxsecurity.com

 

Back to Top