Skip to content

Instantly share code, notes, and snippets.

@hamoshwani
Created September 27, 2022 19:28
Show Gist options
  • Save hamoshwani/44653bfe7b8cc461692a2f074b1ef475 to your computer and use it in GitHub Desktop.
Save hamoshwani/44653bfe7b8cc461692a2f074b1ef475 to your computer and use it in GitHub Desktop.
Employee can exploit XSS into local file read using PDF generator in Zkteco Biotime
Security Advisory
Topic: Employee can exploit XSS into local file read using PDF generator in Zkteco Biotime
Category: Zkteco Biotime
Module: webgui
Announced: 01-09-2022
Credits: Ahmed Kameran From https://technobase.krd/ -- https://twitter.com/hamoshwani
CVE ID: CVE-2022-38803
Affects: BioTime - < 8.5.3 Build:20200816.447
Corrected: BioTime - > 8.5.3 Build:20200816.447
1. Background
BioTime 8.0 is a powerful web-based time and attendance management software that provides a stable connection to ZKTeco's
standalone push communication devices by Ethernet/Wi-Fi/GPRS/3G and working as a private cloud to
offer employee self-service by mobile application and web browser.
2. Problem Description
A Cross-Site Scripting (XSS) vulnerabilities was found in
BioTime BioTime - < 8.5.3 Build:20200816.447 that could lead to local file read when an employee try to export injected payload using pdf
the pdf generator will simply execute the javascript code inside the injected payload that can lead to Local file read
Vulenrable models:
1- When requesting for leave
Parameter: reason
2- When requesting for overtime
Parameter: reason
3- When requesting for Manual log
Parameter: reason
3. Impact
Due to the lack of proper encoding on the affected parameters susceptible to
XSS, arbitrary JavaScript could be executed by pdf generator's headless browser that could lead to local file read
4. Solution
Users can upgrade to 8.5.4 or later.
Please find latest version from the Zkteco main website or they provide hardcopy of the software when you buy an Iface or any attendance devices make sure
You install versions higher than 8.5.3
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment