LiveActive security incident?Get immediate response
CVE Record

CVE-2023-52163: Digiever DS-2105 Pro 3.1.0.71-11 devices allow time_tzsetup.cgi Command Injection.

Digiever 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.

HighCVSS 8.8Known exploitedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This issue affects Digiever DS-2105 Pro 3.1.0.71-11 devices and can allow command injection through a device CGI endpoint. CISA lists it in KEV, so exploitation is confirmed. The affected product is described as unsupported, making replacement or strict isolation more realistic than relying on routine patching.

Executive priority

Treat this as urgent for exposed devices because CISA KEV confirms exploitation and the product is unsupported. Prioritize finding, isolating, and replacing affected devices over waiting for a normal patch cycle.

Technical view

CVE-2023-52163 is a high-severity command injection issue in Digiever DS-2105 Pro 3.1.0.71-11 time_tzsetup.cgi. CVSS 3.1 is 8.8 with network access, low complexity, low privileges, no user interaction, and high CIA impact. The source metadata also lists CWE-862, indicating an authorization-related weakness.

Likely exposure

Highest exposure is internet-reachable or broadly reachable Digiever DS-2105 Pro 3.1.0.71-11 devices, especially where accounts exist with low privileges. Evidence does not identify other affected products.

Exploitation context

Active exploitation is supported by CISA KEV. Fortinet’s referenced advisory also frames related activity around IoT devices, but the bundle does not provide enough detail to describe techniques, scale, or specific attacker procedures.

Researcher notes

The record names command injection, while the CWE is CWE-862. Affected CPE data is absent, so validation should rely on model and firmware evidence. Do not generalize beyond Digiever DS-2105 Pro 3.1.0.71-11 without vendor confirmation.

Mitigation direction

  • Inventory for Digiever DS-2105 Pro 3.1.0.71-11 devices.
  • Remove affected unsupported devices from internet exposure.
  • Restrict access to trusted management networks only.
  • Plan replacement or retirement of unsupported affected hardware.
  • Check vendor and referenced advisories for any available guidance.
  • Monitor for unusual device administration or outbound activity.

Validation and detection

  • Confirm device model and firmware version from asset records.
  • Check external exposure using approved asset inventory tooling.
  • Review access controls around device management interfaces.
  • Look for evidence of unexpected configuration or account changes.
  • Compare findings against CISA KEV and referenced advisories.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-52163 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
Yes
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2023-52163Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.