CVE-2023-52163
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 · uneditedDigiever DS-2105 Pro 3.1.0.71-11 devices allow time_tzsetup.cgi Command Injection. 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 · high confidenceCommand injection vulnerability in the time_tzsetup.cgi endpoint of Digiever DS-2105 Pro NVR devices (version 3.1.0.71-11) allows remote attackers to execute arbitrary operating system commands via unsanitized input. The CVSS 8.8 score reflects high exploitability and significant impact on confidentiality, integrity, and availability.
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= 3.1.0.71-11= 3.1.0.71-11CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify device modelAccess the NVR web interface or check device documentation to confirm the exact model is Digiever DS-2105 Pro or DS-2105 Pro+.Affected if Device is not a Digiever DS-2105 Pro or DS-2105 Pro+ model.
-
Check firmware versionLog into the NVR admin interface and navigate to System > System Information > Firmware Version, or access the device via SSH and run 'cat /etc/version' or 'version' command to determine the installed firmware version.Affected if Firmware version is exactly 3.1.0.71-11.
-
Locate time_tzsetup.cgi scriptAccess the web interface and navigate to the CGI endpoint path, typically at /cgi-bin/time_tzsetup.cgi, or check the device filesystem via SSH for the presence of this script in the /www/cgi-bin/ or /cgi-bin/ directory.Affected if The time_tzsetup.cgi script exists and is accessible on the device.
-
Verify CGI interface accessibilityAttempt to access http://[device-ip]/cgi-bin/time_tzsetup.cgi from a browser or use curl to send a request to the CGI endpoint to confirm it responds.Affected if The CGI script responds to HTTP requests, indicating it is enabled and accessible.
-
Assess network exposureCheck firewall rules, ACLs, or VLAN configuration to determine if the device web interface and CGI scripts are accessible from untrusted networks or the internet.Affected if The device web interface (port 80/443) is reachable from untrusted networks without proper access controls.
A user is affected if they have a Digiever DS-2105 Pro or DS-2105 Pro+ NVR running firmware version 3.1.0.71-11 with the time_tzsetup.cgi script accessible over 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 · scopedThis is an end-of-life product receiving no security updates; immediate network isolation or segmentation is required, followed by replacement with a supported device from a vendor providing regular security patches.
- Replace the end-of-life Digiever DS-2105 Pro/Pro+ devices with currently supported surveillance hardware from Digiever or an alternative vendor
- If immediate replacement is not feasible, isolate affected devices on a restricted network segment with strict firewall rules limiting access to trusted management IPs only
- Disable any unnecessary network services and CGI interfaces on the affected devices if the web interface cannot be disabled
- Implement additional network monitoring and logging for the affected devices to detect potential exploitation attempts
- Consider deploying compensating controls such as intrusion detection/prevention systems (IDS/IPS) on network segments containing these devices
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-52163 — 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-52163 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