CVE-2023-4587
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 · uneditedAn IDOR vulnerability has been found in ZKTeco ZEM800 product affecting version 6.60. This vulnerability allows a local attacker to obtain registered user backup files or device configuration files over a local network or through a VPN server.
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 · moderate confidenceAn IDOR vulnerability in ZKTeco ZEM800 version 6.60 allows authenticated or local network attackers to access sensitive user backup files and device configuration files by manipulating object references in file retrieval requests, without proper authorization validation.
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= 6.60CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the device web interface or check device documentation/labels to confirm the model is ZKTeco ZEM800Affected if The device is not a ZEM800 model - different models are not affected by this CVE
-
Check the installed firmware versionLog into the device web management interface and navigate to System Info or Device Settings to view the firmware versionAffected if The firmware version is 6.60 - only this specific version is affected
-
Verify if the web management interface is enabledAttempt to access the device IP address on the default web port (typically 80 or 443) to confirm the web interface is runningAffected if The web interface is exposed and accessible - the IDOR vulnerability exists in the file retrieval functionality of this interface
-
Check network accessibility of the deviceDetermine if the device management interface is reachable from the network by pinging the device IP and attempting HTTP/HTTPS accessAffected if The device is accessible from network segments beyond its intended management network - this expands the potential attacker reach
-
Assess authentication statusDetermine if default credentials are in use or if authentication is required for the web management interfaceAffected if The device allows authenticated access or has default credentials - the vulnerability allows authorized users to access files they should not have permission to view
You are affected if you have a ZEM800 device running firmware version 6.60 with the web management interface enabled and accessible, regardless of authentication status since authenticated or local network attackers can exploit the IDOR flaw to access unauthorized backup and configuration files.
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.
From vendor dataImplement proper authorization checks for all file access requests to ensure users can only access their own backup files; restrict network access to the device management interface and apply network segmentation.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-4587 — 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-4587 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