dbcve.org
Zkbio MediaApplication · Zkteco

CVE-2024-2318

HIGH · 7.5 CVSS v3.1 Published 2024-03-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability was found in ZKTeco ZKBio Media 2.0.0_x64_2024-01-29-1028. It has been classified as problematic. Affected is an unknown function of the file /pro/common/download of the component Service Port 9999. The manipulation of the argument fileName with the input ../../../../zkbio_media.sql leads to path traversal: '../filedir'. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 2.1.3 Build 2025-05-26-1605 is able to address this issue. It is recommended to upgrade the affected component.

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 confidence

A path traversal vulnerability in ZKTeco ZKBio Media 2.0.0 allows remote attackers to access arbitrary files via the /pro/common/download endpoint on port 9999 by manipulating the fileName parameter with directory traversal sequences (../../../../). The vulnerability has a public exploit and rates 7.5 HIGH on CVSS.

MitigationUpgrade to version 2.1.3 Build 2025-05-26-1605 as the vendor-recommended fix. If immediate patching is not feasible, restrict network access to port 9999 from untrusted sources as a compensating control.

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
Zkbio MediaApplication
Affected:= 2.0.0

CVSS 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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm ZKBio Media is installed
    Check for ZKBio Media installation by querying running processes or installed software on the system. On Windows, check Program Files for 'ZKBio Media' folder or review installed programs. On Linux, check common application directories.
    Affected if ZKBio Media version 2.0.0 is installed and running on the system
  2. Verify the exact version number
    Locate the version information for ZKBio Media. Check application metadata, about dialog, or version file within the installation directory. Compare against the affected version = 2.0.0.
    Affected if The installed version is exactly 2.0.0 (no other versions are affected)
  3. Check if port 9999 is exposed
    Scan the local system or perimeter firewall to determine if port 9999 is open and accessible. Use 'netstat -an | grep 9999' or a port scanner to verify the service is listening externally.
    Affected if Port 9999 is open and accepting external connections from untrusted sources
  4. Confirm the vulnerable endpoint is accessible
    Attempt to access the /pro/common/download endpoint on port 9999 via HTTP (e.g., curl http://target:9999/pro/common/download). A valid HTTP response indicates the endpoint exists.
    Affected if The /pro/common/download endpoint responds to HTTP requests
  5. Test for path traversal vulnerability
    Send a crafted request with directory traversal to the endpoint: http://target:9999/pro/common/download?fileName=../../../../../../windows/win.ini (or /etc/passwd on Linux). A vulnerable system will return the contents of the specified file.
    Affected if The response contains contents of files outside the intended directory, confirming path traversal is possible

A system is affected if ZKBio Media version 2.0.0 is running with port 9999 exposed and the /pro/common/download endpoint responds to path traversal queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 2.1.3 Build 2025-05-26-1605 as the vendor-recommended fix. If immediate patching is not feasible, restrict network access to port 9999 from untrusted sources as a compensating control.

Recommended fix High confidence

2.1.3 Build 2025-05-26-1605

  1. 1. Download ZKBio Media version 2.1.3 Build 2025-05-26-1605 from the official ZKTeco website (www.zkteco.com)
  2. 2. Back up all existing configuration files and database data from the current ZKBio Media 2.0.0 installation
  3. 3. Stop the ZKBio Media service running on port 9999
  4. 4. Uninstall or replace the existing ZKBio Media 2.0.0 installation with version 2.1.3 Build 2025-05-26-1605
  5. 5. Restore the backed-up configuration and data to the new installation
  6. 6. Start the ZKBio Media service
  7. 7. Verify the vulnerability is fixed by attempting the original path traversal request to /pro/common/download with the fileName argument

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zkbio Media Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,620
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,592.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-2318 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-2318 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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