CVE-2023-38951
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedZKTeco BioTime 8.5.5 through 9.x before 9.0.1 (20240617.19506) allows authenticated attackers to create or overwrite arbitrary files on the server via crafted requests to /base/sftpsetting/ endpoints that abuse a path traversal issue in the Username field and a lack of input sanitization on the SSH Key field. Overwriting specific files may lead to arbitrary code execution as NT AUTHORITY\SYSTEM.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceZKTeco BioTime versions 8.5.5 through 9.x before 9.0.1 contains a path traversal vulnerability in the /base/sftpsetting/ endpoint where the Username field accepts path traversal sequences (e.g., ../../../filename), combined with unsanitized input in the SSH Key field. This allows authenticated attackers to write or overwrite arbitrary files on the server filesystem, potentially leading to remote code execution as NT AUTHORITY\SYSTEM by overwriting executable or configuration files.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 8.5.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm BioTime installation and locate executableLook for BioTime installation directories - common paths include C:\Program Files\ZKTeco\BioTime or C:\ZKBioTime. Check for BioTime.exe, BioTimeService.exe, or similar executables in these locations.Affected if BioTime software is found on the system and is version 8.5.5 through 9.x (before 9.0.1)
-
Identify installed BioTime versionRight-click on BioTime.exe or BioTimeService.exe, select Properties, then check the Details tab for the File Version. Alternatively, check the version info from the Windows Programs and Features list, or query the Windows Registry under HKLM\SOFTWARE\ZKTeco\BioTime for the installed version.Affected if The installed version falls within 8.5.5 through 9.0.0 (or any version before 9.0.1)
-
Check if SFTP module is enabledAccess the BioTime web interface and navigate to System Settings > SFTP Settings, or inspect the BioTime configuration database/INI files for SFTP-related configuration entries. Look for SFTP server configuration options.Affected if The SFTP feature is configured or enabled in the BioTime installation
-
Verify endpoint accessibilityAttempt to access the /base/sftpsetting/ endpoint via the BioTime web interface using an authenticated administrative account. Check for the presence of the SFTP settings page where Username and SSH Key fields can be modified.Affected if The /base/sftpsetting/ endpoint is accessible with administrative credentials
You are affected if BioTime version 8.5.5 through 9.0.0 is installed and the SFTP settings interface is accessible to authenticated administrators.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to BioTime version 9.0.1 (20240617.19506) or later which addresses the path traversal and input sanitization issues. If immediate patching is not feasible, restrict administrative access to the SFTP settings interface and monitor for unauthorized file modifications.
BioTime 9.0.1 (20240617.19506)
- Backup the current BioTime installation and database before proceeding with the upgrade
- Download BioTime version 9.0.1 (20240617.19506) from the official ZKTeco website (www.zkteco.com)
- Verify the system meets the requirements for version 9.0.1
- Stop the BioTime services
- Install version 9.0.1 following the standard upgrade procedure
- Start the BioTime services
- Verify the patch was successfully applied by checking the BioTime version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-38951 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-38951 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data