CVE-2019-12182 json
Directory Traversal in Safescan Timemoto and TA-8000 series version 1.0 allows unauthenticated remote attackers to execute code via the adm…
published 2020-03-13 6 y ago modified 2026-06-17 4 mo ago also EUVD-2019-3831
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 5.0%
- EPSS 5.0% chance of exploitation in 30 days, percentile 92%
- public exploits
- 0
- none known
Summary
Directory Traversal in Safescan Timemoto and TA-8000 series version 1.0 allows unauthenticated remote attackers to execute code via the administrative API.
Patch / fix
- safescan ta-8010_firmware 7.0.3.100-ta8000-14
- safescan ta-8015_firmware 7.0.3.100-ta8000-14
- safescan ta-8020_firmware 7.0.3.100-ta8000-14
- safescan ta-8025_firmware 7.0.3.100-ta8000-14
- safescan ta-8030_firmware 7.0.3.100-ta8000-14
- safescan ta-8035_firmware 7.0.3.100-ta8000-14
Exploit prediction
4.98% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/ProCheckUp/SafeScan referenced PoC, tagged "exploit" by a source, unverified
- procheckup.com https://procheckup.com/blogs/posts/2020/february/remote-code-execution-on-biometric-iot-devices/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
github.com
/ProCheckUp/SafeScan
exploit, third-party-advisory
-
procheckup.com
/blogs/posts/2020/february/remote-code-execution-on-biometric-iot-devices/
exploit, third-party-advisory
-
support.timemoto.com
/en/s/safescan-time-clock-systems/a/firmware-update-7-dot-03-dot-100-ta8000-14
vendor-advisory
-
safescan.com
/
product
Sources
- CVE List CVE-2019-12182
- NVD CVE-2019-12182
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.