dbcve.org
Cp Uvr 1601e1 Hc FirmwareOperating system · Cpplusworld

CVE-2023-3704

MEDIUM · 5.3 CVSS v3.1 Published 2023-08-24
Fix available
A fix is available. Upgrade to 4.000.00at008.0.0.r20230302 or later.
See remediation →
62/100
Remediation priority · Elevated
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
The vulnerability exists in CP-Plus DVR due to an improper input validation within the web-based management interface of the affected products. An unauthenticated remote attacker could exploit this vulnerability by sending specially crafted HTTP requests to the vulnerable device. Successful exploitation of this vulnerability could allow the remote attacker to change system time of the targeted device.

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

This is an improper input validation vulnerability in CP-Plus DVR devices' web-based management interface. An unauthenticated remote attacker can exploit it by sending specially crafted HTTP requests to change the device's system time.

MitigationRestrict network access to the web management interface using firewall rules or network segmentation, and contact CP-Plus for a firmware patch to address the input validation flaw.

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
Cp Uvr 1601e1 Hc FirmwareOperating system
Affected:< 4.000.00at008.0.0.r20230302
Cp Uvr 0401l1 4kh FirmwareOperating system
Affected:< 4.000.00at008.0.0.r20230302
Cp Uvr 0401l1b 4kh FirmwareOperating system
Affected:< 4.000.00at008.0.0.r20230302
Cp Uvr 0801f1 Hc FirmwareOperating system
Affected:< 4.000.00at008.0.0.r20230302
Cp Uvr 0801k1 H FirmwareOperating system
Affected:< 4.000.00at008.0.0.r20230302
Cp Uvr 0801k1b H FirmwareOperating system
Affected:< 4.000.00at008.0.0.r20230302
Cp Uvr 0808k1 H FirmwareOperating system
Affected:< 4.000.00at008.0.0.r20230302
Cp Uvr 1601e1 H FirmwareOperating system
Affected:< 4.000.00at008.0.0.r20230302

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checks

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

  1. Identify CP-Plus DVR devices on your network
    Scan your network for devices with HTTP/HTTPS ports open that respond with CP-Plus DVR web interface. Look for devices matching model numbers: Cp Uvr 1601e1, Cp Uvr 0401l1, Cp Uvr 0401l1b, Cp Uvr 0801f1, Cp Uvr 0801k1, Cp Uvr 0801k1b, Cp Uvr 0808k1.
    Affected if Any of these specific CP-Plus DVR models are found on the network with their web management interface exposed.
  2. Access the device web interface
    Navigate to the IP address of the identified DVR device using a web browser over HTTP or HTTPS. Log into the management interface if credentials are known.
    Affected if The web-based management interface is accessible, indicating the vulnerable component is exposed.
  3. Check firmware version
    Locate the firmware version information in the device web interface. This is typically found under System, Settings, Device Info, or About sections. Note the exact version string displayed.
    Affected if The displayed firmware version is lower than 4.000.00at008.0.0.r20230302, or the version cannot be confirmed to be at or above this threshold.
  4. Verify web interface is network-accessible
    Confirm the DVR web management interface is reachable from network segments beyond the local management VLAN. Test from an external subnet or validate firewall rules allow HTTP/HTTPS access to the device.
    Affected if The web interface is accessible from network segments not intended for device management, making the vulnerability exploitable remotely.

If CP-Plus DVR devices with firmware versions below 4.000.00at008.0.0.r20230302 have their web management interface exposed on the network, the environment is affected by this vulnerability.

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
Upgrade available Upgrade to 4.000.00at008.0.0.r20230302 or later
Fixed in 4.000.00at008.0.0.r20230302
Interim mitigation

Restrict network access to the web management interface using firewall rules or network segmentation, and contact CP-Plus for a firmware patch to address the input validation flaw.

Recommended fix High confidence

Firmware version 4.000.00at008.0.0.r20230302 or later

  1. Identify the exact CP-Plus DVR model from the affected product list (Cp Uvr 1601e1 Hc, Cp Uvr 0401l1 4kh, Cp Uvr 0401l1b 4kh, Cp Uvr 0801f1 Hc, Cp Uvr 0801k1 H, Cp Uvr 0801k1b H, Cp Uvr 0808k1 H, or Cp Uvr 1601e1 H)
  2. Access the device's web-based management interface using an authenticated session
  3. Navigate to the firmware update or system maintenance section of the web interface
  4. Obtain the firmware version 4.000.00at008.0.0.r20230302 or later from the official CP-Plus vendor support渠道
  5. Upload and apply the firmware update following the vendor's documented upgrade procedure
  6. After the firmware update completes, verify the device is running firmware version 4.000.00at008.0.0.r20230302 or later
  7. Verify the system time can no longer be modified via unauthenticated HTTP requests
Caveat Firmware updates on embedded devices may temporarily interrupt video recording; schedule update during maintenance window

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

Fix this in Cp Uvr 1601e1 Hc Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-3704 — 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-2023-3704 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