CVE-2023-52164
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 · uneditedaccess_device.cgi on Digiever DS-2105 Pro 3.1.0.71-11 devices allows arbitrary file read. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.
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 confidenceThe Digiever DS-2105 Pro NVR device running firmware 3.1.0.71-11 contains an arbitrary file read vulnerability in the access_device.cgi web interface component. An unauthenticated attacker can exploit this to read sensitive files from the device's filesystem, potentially exposing configuration data, credentials, or other system files.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 modelCheck the physical device label or access the web interface and look for the model name (Digiever DS-2105 Pro NVR) in the system information or device status pageAffected if The device is a Digiever DS-2105 Pro NVR
-
Check the firmware versionAccess the web interface admin panel and navigate to System > Information or similar to view the firmware version, or query the device via SNMP if configuredAffected if The firmware version is exactly 3.1.0.71-11
-
Verify web interface accessibilityAttempt to access the device's web interface over HTTP/HTTPS from the network where the device is deployedAffected if The web interface (port 80 or 443) is reachable from network segments accessible to untrusted users
-
Confirm vulnerable endpoint existsSend an HTTP GET request to the access_device.cgi endpoint (e.g., http://[device-ip]/cgi/access_device.cgi) and observe the responseAffected if The endpoint responds (even with an error) indicating the CGI component is present
You are affected if the device is a Digiever DS-2105 Pro NVR running firmware version 3.1.0.71-11 with the web interface exposed to the network.
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 · scopedSince the product is end-of-life and no longer supported by the vendor, there are no official patches. Organizations should remove affected devices from production networks, implement strict network segmentation to limit exposure, and replace with currently supported hardware.
- This device model (Digiever DS-2105 Pro) and firmware version 3.1.0.71-11 are end-of-life and no longer supported by the vendor.
- Replace the unsupported device with a currently supported model from Digiever or an alternative vendor.
- If replacement is not immediately possible, isolate the device on a restricted network segment with firewall rules limiting access to trusted IP addresses only.
- Disable remote access to the web interface (access_device.cgi) if not required, or implement additional authentication layers such as VPN access controls.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-52164 — 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-52164 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