Exploit Title: ZKTime Web Software 2.0 - Broken Authentication
CVE-ID: CVE-2017-14680
Vendor Homepage: https://www.zkteco.com/product/ZKTime_Web_2.0_435.html
Vendor of Product: ZKTeco
Affected Product Code: ZKTime Web - 2.0.1.12280
Category: WebApps
Author: Arvind V.
Author Social: @Find_Arvind
 
------------------------------------------
 
Product description:
ZKTime Web 2.0 is a cutting edge Web-based Time Attendance software, which
provided a stable communication for devices through GPRS/WAN, hence, users
can access the software anywhere by their Web Browser to remotely manage
hundreds of T&A terminals under complex network condition (WLAN). The
Application has an administrator role and application user role.
 
Attack Description:
The Application is a time attendance software which allows users to
download their time and attendance data from the application in a PDF
Format. The data includes their employeeas id, user-id, gender,
birth-dates, phone numbers and access-areas. These PDF Files however are
not properly authenticated. If any user get access to the file-download
link, he can go ahead and download these files directly without any
authentication.
 
Proof of Concept Links:
 
1) https://XX.XX.XX.XX:8081/tmp/report_file/Personnel_20170820144237.pdf
<https://xx.xx.xx.xx:8081/tmp/report_file/Personnel_20170820144237.pdf>
2) https://XX.XX.XX.XX:8081/tmp/report_file/Personnel_20170820144238.pdf
<https://xx.xx.xx.xx:8081/tmp/report_file/Personnel_20170820144238.pdf>
3) https://XX.XX.XX.XX:8081/tmp/report_file/Personnel_20170820144239.pdf
<https://xx.xx.xx.xx:8081/tmp/report_file/Personnel_20170820144239.pdf>
 
 
Impact:
Personal details pertaining to the employees of the company are disclosed
without their permissions. This leads to violation of user privacy.
Moreover the information available can be used to mount further attacks.
 
References:
https://seclists.org/fulldisclosure/2017/Sep/39
https://seclists.org/bugtraq/2017/Sep/20
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14680
 
 
Vulnerability Timeline:
18th August 2017 a Vulnerability Discovered
20th August 2017 a Contacted Vendor a No Response
1st September 2017 a Contacted Vendor again a No Response
18th September 2017 a Vulnerability Disclosed