ZKTeco ZKTime Web 2.0.1.12280 Information Disclosure
Posted on 19 September 2017
*Vulnerability Type*: Broken Authentication *Vendor of Product*: ZKTeco *Affected Product Code Base*: ZKTime Web - 2.0.1.12280 *Affected Component*: ZK Time Web Interface Management. *Attack Type*: Local - Unauthenticated *Impact*: Information Disclosure ------------------------------------------ *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). *Attack Scenario:* 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 Code:* Broken Links: http://XX.XX.XX.XX:8081/tmp/report_file/Personnel_20170820144237.pdf <http://xx.xx.xx.xx:8081/tmp/report_file/Personnel_20170820144237.pdf> http://XX.XX.XX.XX:8081/tmp/report_file/Personnel_20170820144238.pdf <http://xx.xx.xx.xx:8081/tmp/report_file/Personnel_20170820144238.pdf> http://XX.XX.XX.XX:8081/tmp/report_file/Personnel_20170820144239.pdf <http://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. *Recommendation:* All the links and URLas of the application should be appropriately protected. *Credit*: Arvind Vishwakarma http://ultimateone1.blogspot.ae/ *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
